by HonkWatch

Is Fibertime down?

No. Fibertime is working. Updated 4 Nov, 12:39 UTC, 8 min ago · No status page: this is what our own checks see Last problem: 4 Nov, 12:31 UTC, major outage for 8 min (Could not be loaded from 27 of 34 cities).
Having trouble with Fibertime?

Last 9030 days

Collecting since 4 Nov; the uptime figure shows after the first hour of readings

Of the last 90 days, 1 had a partial or major outage, 0 had maintenance only and 89 have no data. Recent problems are listed in a table further down.

90 days ago30 days agoToday

No problems Partial outage Major outage Maintenance No data yet

Last 24 hours

Every 15 minutes, hours in UTC

Bars: the share of our own checks of fibertime.com that failed (1,356 checks). Shaded: when our checks showed Fibertime with a problem. We don't collect user reports.

0%43%86% 18:0000:0006:0012:00 35% of 161 checks failed55% of 244 checks failed62% of 276 checks failed67% of 227 checks failed50% of 209 checks failed56% of 204 checks failed86% of 35 checks failed

Our own checks of fibertime.com

Every 5 minutes, from our probes

29 of 34 cities can't reach fibertime.com.

New York: loaded in 1942 ms Mumbai: loaded in 9670 ms Doha: loaded in 5617 ms Seattle: loaded in 5378 ms Lauterbourg: loaded in 1733 ms New Jersey: could not load it (TimeoutError: Check took longer than 10 s) Johannesburg: could not load it (TimeoutError: Check took longer than 10 s) Dallas: could not load it (TimeoutError: Check took longer than 10 s) Jakarta: could not load it (TimeoutError: Check took longer than 10 s) Melbourne: could not load it (TimeoutError: Check took longer than 10 s) Delhi: could not load it (TimeoutError: Check took longer than 10 s) Santiago: could not load it (TimeoutError: Check took longer than 10 s) Sydney: could not load it (TimeoutError: Check took longer than 10 s) Osaka: could not load it (TimeoutError: Check took longer than 10 s) Seoul: could not load it (TimeoutError: Check took longer than 10 s) Amsterdam: could not load it (TimeoutError: Check took longer than 10 s) London: could not load it (TimeoutError: Check took longer than 10 s) Frankfurt: could not load it (TimeoutError: Check took longer than 10 s) Madrid: could not load it (TimeoutError: Check took longer than 10 s) Hamina: could not load it (TimeoutError: Check took longer than 10 s) Bangalore: could not load it (TimeoutError: Check took longer than 10 s) Singapore: could not load it (TimeoutError: Check took longer than 10 s) Tel Aviv: could not load it (TimeoutError: Check took longer than 10 s) Tokyo: could not load it (TimeoutError: Check took longer than 10 s) Warsaw: could not load it (TimeoutError: Check took longer than 10 s) Portsmouth: could not load it (TimeoutError: Check took longer than 10 s) Querétaro: could not load it (TimeoutError: Check took longer than 10 s) Los Angeles: could not load it (TimeoutError: Check took longer than 10 s) Hong Kong: could not load it (TimeoutError: Check took longer than 10 s) Toronto: could not load it (TimeoutError: Check took longer than 10 s) St. Louis: could not load it (TimeoutError: Check took longer than 10 s) Cape Town: could not load it (TimeoutError: Check took longer than 10 s) Atlanta: could not load it (TimeoutError: Check took longer than 10 s) São Paulo: could not load it (TimeoutError: Check took longer than 10 s)
  • New YorkReachable1942 ms, just now
  • New JerseyNo answer within 10 s10048 ms, just now
  • JohannesburgNo answer within 10 s10000 ms, just now
  • DallasNo answer within 10 s10001 ms, just now
  • JakartaNo answer within 10 s10001 ms, just now
  • MelbourneNo answer within 10 s10000 ms, just now
  • DelhiNo answer within 10 s10000 ms, just now
  • SantiagoNo answer within 10 s10000 ms, just now
  • SydneyNo answer within 10 s10000 ms, just now
  • OsakaNo answer within 10 s10001 ms, just now
  • SeoulNo answer within 10 s10001 ms, just now
  • AmsterdamNo answer within 10 s10001 ms, just now
  • LondonNo answer within 10 s10001 ms, just now
  • FrankfurtNo answer within 10 s10001 ms, just now
  • MadridNo answer within 10 s10001 ms, just now
  • HaminaNo answer within 10 s10001 ms, just now
  • BangaloreNo answer within 10 s10001 ms, just now
  • SingaporeNo answer within 10 s10001 ms, just now
  • Tel AvivNo answer within 10 s10001 ms, just now
  • TokyoNo answer within 10 s10001 ms, just now
  • WarsawNo answer within 10 s10001 ms, just now
  • PortsmouthNo answer within 10 s10001 ms, just now
  • QuerétaroNo answer within 10 s10001 ms, just now
  • Los AngelesNo answer within 10 s10001 ms, just now
  • Hong KongNo answer within 10 s10001 ms, just now
  • TorontoNo answer within 10 s10001 ms, just now
  • St. LouisNo answer within 10 s10001 ms, just now
  • Cape TownNo answer within 10 s10001 ms, just now
  • AtlantaNo answer within 10 s10001 ms, just now
  • São PauloNo answer within 10 s10001 ms, just now
  • MumbaiReachable9670 ms, just now
  • DohaReachable5617 ms, just now
  • SeattleReachable5378 ms, just now
  • LauterbourgReachable1733 ms, just now

We load fibertime.com the way a visitor would and note whether it answers.

No status page

Fibertime does not publish a status page, so there is nothing for us to read. What you see here is what we measure ourselves: its website is loaded from our probes in 34 cities every 5 minutes. We show a problem when a quarter of the cities that are working normally can't load it, and an outage when half can't. A city that has not been able to load it once in the last two days is left out: some sites only open for people in their own country, and that is not an outage. When too few cities are left, we say we can't tell.

Recent problems

4 Nov, 12:31 UTCMajor outage8 minCould not be loaded from 27 of 34 cities
4 Nov, 12:07 UTCMajor outage8 minCould not be loaded from 18 of 34 cities

Alert me when Fibertime is down

HonkWatch can load Fibertime's website for you from several cities and alert you by email, Slack, Discord or Telegram when it stops answering.

Start free Log in

More in Telecom and internet

Questions

Is Fibertime down, or is it just me?

Our checks reach Fibertime's website from most of our cities. If it isn't working for you, the cause is more likely near you: your network, your browser, or a problem only in your area. Try another network or device.

How do we know?

Fibertime has no public status page. We load fibertime.com from our own probes in several cities and note whether it answers. We don't guess from social media posts or reports.

How often do we check?

The website every 5 minutes, day and night. We keep 90 days of history: a day we have no reading for shows as "no data yet", never as working.

Our own checks of the Fibertime website. HonkWatch also checks websites from 34 cities.

← All services