by HonkWatch

Is Openserve down in South Africa?

Openserve problems reported by people in South Africa. Check the last 24 hours and tell others what isn't working for you.

Having trouble with Openserve?

Tell others what's happening. No account needed.

What isn't working?

One report per service per hour. Reports are anonymous; your IP address is not stored in the report.

Reports from people in South Africa

Last 24 hours · South Africa · times in UTC

1 report

0 reports in the latest hour shown. Reports reflect people's experiences; they do not by themselves confirm an outage.

024 18:0000:0006:0012:00 1 report

Reports per 15 minutes. A flat chart means no reports, not proof that everything works.

What people report

  • Not specified1 · 100%

Compare worldwide reports · Other services in South Africa

Website checks — worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for South Africa. The report chart above is filtered to South Africa.

Our checks can reach the Openserve website. Loads in South Africa. Most of our other places are refused, as usual for this website. Updated 5 Nov, 15:26 UTC, 3 min ago · Website checks: these do not test every feature Website reachability does not confirm that sign-in, payments, messaging or the app is working. Last problem: 4 Nov, 17:33 UTC, partial outage for 21 min (Could not be loaded from 9 of 34 cities).

Having trouble with Openserve?

  1. Compare reports from South Africa and check the latest update above. A quiet chart does not rule out a new or local problem.
  2. Try the service on another device or switch between WiFi and mobile data, if available. If other sites also fail, check your internet provider.
  3. Report a problem with the feature that is failing and the country where you are affected. Submit once; your report appears in the chart.

Reports describe people's experiences. One report alone does not confirm an outage.

Where people report problems worldwide

Where people report it

Reports by country over the last 24 hours.

South Africa: 1 report in the last 24 hours

South Africa 1

Last 9030 days

88.61% of the time without a reported outage, since 4 Nov

Of the last 90 days, 1 had a partial or major outage, 0 had maintenance only and 88 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 (27,043 checks). Shaded: when our checks showed Openserve with a problem. Community reports appear separately above, alongside our checks and provider updates.

0%41%82% 18:0000:0006:0012:00 78% of 402 checks failed80% of 432 checks failed82% of 397 checks failed78% of 417 checks failed76% of 302 checks failed78% of 395 checks failed77% of 319 checks failed79% of 314 checks failed82% of 401 checks failed70% of 348 checks failed58% of 235 checks failed70% of 317 checks failed55% of 246 checks failed63% of 263 checks failed66% of 255 checks failed64% of 270 checks failed64% of 203 checks failed68% of 302 checks failed64% of 293 checks failed64% of 272 checks failed65% of 289 checks failed64% of 261 checks failed58% of 232 checks failed61% of 231 checks failed63% of 260 checks failed68% of 278 checks failed67% of 279 checks failed69% of 299 checks failed60% of 247 checks failed62% of 267 checks failed67% of 314 checks failed63% of 251 checks failed67% of 302 checks failed65% of 272 checks failed59% of 261 checks failed64% of 284 checks failed63% of 252 checks failed65% of 286 checks failed61% of 259 checks failed60% of 262 checks failed66% of 262 checks failed61% of 249 checks failed68% of 303 checks failed57% of 235 checks failed66% of 283 checks failed62% of 283 checks failed64% of 267 checks failed67% of 310 checks failed63% of 268 checks failed61% of 251 checks failed64% of 284 checks failed65% of 266 checks failed63% of 275 checks failed63% of 272 checks failed68% of 301 checks failed67% of 310 checks failed68% of 287 checks failed62% of 265 checks failed63% of 273 checks failed68% of 288 checks failed63% of 258 checks failed61% of 263 checks failed65% of 263 checks failed71% of 342 checks failed64% of 288 checks failed63% of 262 checks failed61% of 277 checks failed62% of 284 checks failed63% of 270 checks failed61% of 258 checks failed62% of 270 checks failed61% of 274 checks failed67% of 295 checks failed62% of 268 checks failed58% of 231 checks failed63% of 266 checks failed55% of 232 checks failed69% of 309 checks failed62% of 265 checks failed70% of 273 checks failed68% of 276 checks failed62% of 251 checks failed70% of 282 checks failed66% of 287 checks failed67% of 304 checks failed57% of 238 checks failed61% of 267 checks failed67% of 284 checks failed59% of 247 checks failed68% of 320 checks failed66% of 284 checks failed58% of 224 checks failed64% of 273 checks failed65% of 277 checks failed66% of 262 checks failed65% of 218 checks failed

Our own checks of openserve.co.za

Every 5 minutes, from our probes

18 of 35 cities can't reach openserve.co.za.

Santiago: loaded in 15457 ms Johannesburg: loaded in 7787 ms Hamina: loaded in 15422 ms Atlanta: loaded in 17491 ms Singapore: loaded in 7069 ms Warsaw: loaded in 4836 ms Querétaro: loaded in 5737 ms Portsmouth: loaded in 8601 ms Toronto: loaded in 10685 ms Madrid: loaded in 8172 ms São Paulo: loaded in 8937 ms Frankfurt: loaded in 9989 ms Melbourne: loaded in 14816 ms Tel Aviv: loaded in 8344 ms St. Louis: loaded in 7471 ms Bangalore: loaded in 3954 ms Jakarta: loaded in 14264 ms New Jersey: could not load it (RemoteDisconnected: Remote end closed connection without res) New York: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Dallas: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Sydney: could not load it (RemoteDisconnected: Remote end closed connection without res) Doha: could not load it (RemoteDisconnected: Remote end closed connection without res) Delhi: could not load it (RemoteDisconnected: Remote end closed connection without res) Hong Kong: could not load it (RemoteDisconnected: Remote end closed connection without res) Cape Town: could not load it (RemoteDisconnected: Remote end closed connection without res) Seoul: could not load it (RemoteDisconnected: Remote end closed connection without res) Tokyo: could not load it (RemoteDisconnected: Remote end closed connection without res) Osaka: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer) Amsterdam: could not load it (TimeoutError: Check took longer than 20 s) Lauterbourg: could not load it (TimeoutError: Check took longer than 20 s) Los Angeles: could not load it (RemoteDisconnected: Remote end closed connection without res) Port Louis: could not load it (TimeoutError: Check took longer than 20 s) Seattle: could not load it (RemoteDisconnected: Remote end closed connection without res) Mumbai: could not load it (RemoteDisconnected: Remote end closed connection without res) London: could not load it (ConnectionResetError: [Errno 104] Connection reset by peer)
  • New JerseyServer closed the connection1254 ms, just now
  • New YorkConnection reset by the server1191 ms, just now
  • SantiagoReachable15457 ms, just now
  • JohannesburgReachable7787 ms, just now
  • DallasConnection reset by the server1253 ms, just now
  • SydneyServer closed the connection1913 ms, just now
  • DohaServer closed the connection658 ms, just now
  • DelhiServer closed the connection1124 ms, just now
  • Hong KongServer closed the connection1570 ms, just now
  • Cape TownServer closed the connection136 ms, just now
  • SeoulServer closed the connection1429 ms, 1 min ago
  • TokyoServer closed the connection1723 ms, 1 min ago
  • OsakaConnection reset by the server1362 ms, 1 min ago
  • HaminaReachable15422 ms, 1 min ago
  • AmsterdamNo answer within 20 s20000 ms, 1 min ago
  • AtlantaReachable17491 ms, 1 min ago
  • LauterbourgNo answer within 20 s20108 ms, 1 min ago
  • Los AngelesServer closed the connection1516 ms, 2 min ago
  • SingaporeReachable7069 ms, 2 min ago
  • WarsawReachable4836 ms, 2 min ago
  • QuerétaroReachable5737 ms, 2 min ago
  • PortsmouthReachable8601 ms, 2 min ago
  • TorontoReachable10685 ms, 3 min ago
  • Port LouisNo answer within 20 s20001 ms, 3 min ago
  • SeattleServer closed the connection1469 ms, 3 min ago
  • MadridReachable8172 ms, 4 min ago
  • São PauloReachable8937 ms, 4 min ago
  • MumbaiServer closed the connection798 ms, 4 min ago
  • LondonConnection reset by the server1340 ms, 4 min ago
  • FrankfurtReachable9989 ms, 7 min ago
  • MelbourneReachable14816 ms, 7 min ago
  • Tel AvivReachable8344 ms, 8 min ago
  • St. LouisReachable7471 ms, 8 min ago
  • BangaloreReachable3954 ms, 8 min ago
  • JakartaReachable14264 ms, 8 min ago

We request openserve.co.za and note whether it answers. These automated checks do not sign in or use the app's features.

Available evidence

We check whether its website loads every 5 minutes. This does not test sign-in, payments, calls or every feature of its app or network. We show a website problem when a quarter of the eligible places cannot load it, and an outage when half cannot. Places that normally cannot reach it are excluded. With too few results, we say we cannot tell.

Recent problems

4 Nov, 17:33 UTCPartial outage21 minCould not be loaded from 9 of 34 cities
4 Nov, 17:25 UTCMajor outage8 minCould not be loaded from 19 of 34 cities
4 Nov, 17:17 UTCPartial outage8 minCould not be loaded from 12 of 34 cities
4 Nov, 16:37 UTCPartial outage16 minCould not be loaded from 14 of 34 cities
4 Nov, 16:30 UTCMajor outage8 minCould not be loaded from 21 of 34 cities
4 Nov, 16:06 UTCPartial outage8 minCould not be loaded from 12 of 34 cities
4 Nov, 15:50 UTCPartial outage8 minCould not be loaded from 16 of 34 cities
4 Nov, 15:25 UTCMajor outage8 minCould not be loaded from 25 of 34 cities
4 Nov, 14:20 UTCMajor outage29 minCould not be loaded from 22 of 34 cities
4 Nov, 14:12 UTCPartial outage8 minCould not be loaded from 10 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?

Our checks reach Openserve's website from most of our cities. This does not rule out problems with sign-in, payments, an app or a local network. Check the community reports above and report your experience.

How do we know?

No official status feed is connected for Openserve. We load openserve.co.za from our probes and note whether it answers. People can report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

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

Our own checks of the Openserve website.

← All services