Bergens Tidende is up and responding in 70 ms.
Checked 3 minutes ago · monitored around the clock · bt.no
24-hour uptime: 100%
Is it Bergens Tidende, or is it you? Test your own connection against Bergens Tidende — one verdict in 10 seconds.Bergens Tidende is up and responding in 70 ms. That reading is from itsnotyou's monitoring servers, 3 minutes ago.
It can be either — that's the hard part. The status on this page is measured from itsnotyou's monitoring servers, so Bergens Tidende can look healthy here while your own connection is the real problem. The itsnotyou test checks both at once and returns a single verdict in about 10 seconds.
A slow Bergens Tidende usually comes down to one of two things: Bergens Tidende's own servers are responding slowly — itsnotyou measures time to first byte, and anything over 1500 ms is flagged as slow — or your local connection is the bottleneck. Running the test tells the two apart.
Bergens Tidende is probed every few minutes, around the clock, from itsnotyou's monitoring servers. The verdict and the 24-hour response-time history on this page update automatically.