by HonkWatch

Is Openserve down?

Yes, Openserve has a partial outage. Could not be loaded from 10 of 34 cities. Going on for 4 min. Updated 4 Nov, 12:42 UTC, 4 min ago · No status page: this is what our own checks see
Having trouble with Openserve?

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 openserve.co.za that failed (2,391 checks). Shaded: when our checks showed Openserve with a problem. We don't collect user reports.

0%41%82% 18:0000:0006:0012:00 82% of 300 checks failed80% of 413 checks failed79% of 409 checks failed78% of 437 checks failed79% of 408 checks failed78% of 367 checks failed65% of 57 checks failed

Our own checks of openserve.co.za

Every 5 minutes, from our probes

8 of 34 cities can't reach openserve.co.za.

Tel Aviv: loaded in 2915 ms Seoul: loaded in 4377 ms Osaka: loaded in 9664 ms Portsmouth: loaded in 7614 ms Lauterbourg: loaded in 2944 ms London: loaded in 3370 ms Hamina: loaded in 6190 ms Johannesburg: loaded in 5606 ms New Jersey: loaded in 9475 ms Los Angeles: loaded in 7353 ms Cape Town: loaded in 8238 ms São Paulo: loaded in 5958 ms Amsterdam: loaded in 3360 ms Seattle: loaded in 7252 ms Tokyo: loaded in 5576 ms Jakarta: loaded in 6646 ms Frankfurt: loaded in 4556 ms Warsaw: loaded in 6652 ms Bangalore: loaded in 9897 ms Hong Kong: loaded in 8372 ms Mumbai: loaded in 8838 ms Atlanta: loaded in 6092 ms Delhi: loaded in 7996 ms Madrid: loaded in 6030 ms Sydney: loaded in 4529 ms Dallas: loaded in 3752 ms St. Louis: could not load it (TimeoutError: Check took longer than 10 s) Melbourne: could not load it (TimeoutError: Check took longer than 10 s) New York: could not load it (TimeoutError: Check took longer than 10 s) Doha: could not load it (RemoteDisconnected: Remote end closed connection without res) Querétaro: could not load it (TimeoutError: Check took longer than 10 s) Toronto: could not load it (TimeoutError: Check took longer than 10 s) Singapore: could not load it (TimeoutError: Check took longer than 10 s) Santiago: could not load it (TimeoutError: Check took longer than 10 s)
  • St. LouisNo answer within 10 s10209 ms, just now
  • MelbourneNo answer within 10 s10001 ms, just now
  • New YorkNo answer within 10 s10001 ms, just now
  • DohaServer closed the connection476 ms, just now
  • QuerétaroNo answer within 10 s10001 ms, just now
  • TorontoNo answer within 10 s10001 ms, just now
  • SingaporeNo answer within 10 s10001 ms, just now
  • SantiagoNo answer within 10 s10001 ms, 1 min ago
  • Tel AvivReachable2915 ms, 1 min ago
  • SeoulReachable4377 ms, 1 min ago
  • OsakaReachable9664 ms, 1 min ago
  • PortsmouthReachable7614 ms, 1 min ago
  • LauterbourgReachable2944 ms, 1 min ago
  • LondonReachable3370 ms, 2 min ago
  • HaminaReachable6190 ms, 2 min ago
  • JohannesburgReachable5606 ms, 2 min ago
  • New JerseyReachable9475 ms, 2 min ago
  • Los AngelesReachable7353 ms, 2 min ago
  • Cape TownReachable8238 ms, 2 min ago
  • São PauloReachable5958 ms, 2 min ago
  • AmsterdamReachable3360 ms, 2 min ago
  • SeattleReachable7252 ms, 2 min ago
  • TokyoReachable5576 ms, 2 min ago
  • JakartaReachable6646 ms, 2 min ago
  • FrankfurtReachable4556 ms, 2 min ago
  • WarsawReachable6652 ms, 2 min ago
  • BangaloreReachable9897 ms, 2 min ago
  • Hong KongReachable8372 ms, 2 min ago
  • MumbaiReachable8838 ms, 2 min ago
  • AtlantaReachable6092 ms, 2 min ago
  • DelhiReachable7996 ms, 2 min ago
  • MadridReachable6030 ms, 2 min ago
  • SydneyReachable4529 ms, 2 min ago
  • DallasReachable3752 ms, 2 min ago

We load openserve.co.za the way a visitor would and note whether it answers.

No status page

Openserve 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:42 UTCPartial outagegoing on, 4 minCould not be loaded from 10 of 34 cities
4 Nov, 12:25 UTCMajor outage9 minCould not be loaded from 18 of 34 cities
4 Nov, 12:17 UTCPartial outage8 minCould not be loaded from 9 of 34 cities
4 Nov, 12:10 UTCMajor outage8 minCould not be loaded from 27 of 34 cities

Alert me when Openserve is down

HonkWatch can load Openserve'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 Openserve down, or is it just me?

Many of our cities can't load Openserve's website right now, so it is probably not just you.

How do we know?

Openserve has no public status page. We load openserve.co.za 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 Openserve website. HonkWatch also checks websites from 34 cities.

← All services