by HonkWatch

Is APUA inet down in Côte d'Ivoire?

No problems reported with APUA inet right now

Côte d'Ivoire No reports in the last hour checked 7 min ago
Our checks can reach the APUA inet website. Updated 6 Nov, 18:12 UTC, 7 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.
Report a problemFollow community reports
Change country

Reports from people in Côte d'Ivoire

Last 24 hours · Côte d'Ivoire · times in UTC

0 reports

No community reports in the last 24 hours from Côte d'Ivoire. Having trouble? Add your report.

024 00:0006:0012:0018:00

Bars: reports every 15 minutes. Reports alone do not confirm an outage; a flat chart does not prove everything works.

Report totals as of 6 Nov, 18:19 UTC

Report a problem with APUA inet

Having trouble? Tap what isn't working. No account needed.

What isn't working?

Anonymous · one report per service per hour. This adds your experience to the chart, without contacting the provider or subscribing you to alerts.

Compare worldwide reports · Other services in Côte d'Ivoire

Monitor the website with HonkWatch

Get monitoring alerts for APUA inet

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

Free account required. APUA inet is selected on the next page. Review the monitor and choose where alerts go. Community reports do not trigger these monitoring alerts.

Start free Log in

Where this status comes from

Website checks — Worldwide

The evidence below covers the provider and our available checks. It is not a separate verdict for Côte d'Ivoire. The report chart above is filtered to Côte d'Ivoire.

Our own checks of apua.ag

Every 5 minutes, from our probes

11 of 34 cities can't reach apua.ag.

Atlanta: loaded in 8469 ms New Jersey: loaded in 4254 ms Osaka: loaded in 4052 ms Tel Aviv: loaded in 6609 ms Mumbai: loaded in 4771 ms Frankfurt: loaded in 7292 ms Warsaw: loaded in 6202 ms Cape Town: loaded in 4603 ms Hamina: loaded in 4006 ms Querétaro: loaded in 3400 ms New York: loaded in 3396 ms St. Louis: loaded in 6616 ms Bangalore: loaded in 3519 ms Johannesburg: loaded in 6426 ms Singapore: loaded in 2771 ms Melbourne: loaded in 6038 ms Madrid: loaded in 2815 ms Toronto: loaded in 5147 ms Doha: loaded in 5066 ms London: loaded in 3866 ms Amsterdam: loaded in 3866 ms Jakarta: loaded in 2329 ms São Paulo: loaded in 2745 ms Portsmouth: could not load it (TimeoutError: Check took longer than 20 s) Los Angeles: could not load it (TimeoutError: Check took longer than 20 s) Sydney: could not load it (TimeoutError: Check took longer than 20 s) Tokyo: could not load it (TimeoutError: Check took longer than 20 s) Seoul: could not load it (TimeoutError: Check took longer than 20 s) Seattle: could not load it (TimeoutError: Check took longer than 20 s) Lauterbourg: could not load it (TimeoutError: Check took longer than 20 s) Santiago: could not load it (TimeoutError: Check took longer than 20 s) Delhi: could not load it (TimeoutError: Check took longer than 20 s) Hong Kong: could not load it (TimeoutError: Check took longer than 20 s) Dallas: could not load it (TimeoutError: Check took longer than 20 s)
  • AtlantaReachable8469 ms, just now
  • New JerseyReachable4254 ms, just now
  • OsakaReachable4052 ms, just now
  • Tel AvivReachable6609 ms, just now
  • MumbaiReachable4771 ms, just now
  • FrankfurtReachable7292 ms, just now
  • WarsawReachable6202 ms, just now
  • Cape TownReachable4603 ms, 1 min ago
  • HaminaReachable4006 ms, 1 min ago
  • QuerétaroReachable3400 ms, 1 min ago
  • New YorkReachable3396 ms, 2 min ago
  • St. LouisReachable6616 ms, 2 min ago
  • BangaloreReachable3519 ms, 3 min ago
  • JohannesburgReachable6426 ms, 3 min ago
  • SingaporeReachable2771 ms, 3 min ago
  • PortsmouthNo answer within 20 s20000 ms, 3 min ago
  • Los AngelesNo answer within 20 s20001 ms, 4 min ago
  • SydneyNo answer within 20 s20001 ms, 4 min ago
  • TokyoNo answer within 20 s20069 ms, 4 min ago
  • SeoulNo answer within 20 s20000 ms, 4 min ago
  • SeattleNo answer within 20 s20001 ms, 5 min ago
  • LauterbourgNo answer within 20 s19974 ms, 5 min ago
  • SantiagoNo answer within 20 s20001 ms, 5 min ago
  • DelhiNo answer within 20 s20001 ms, 5 min ago
  • Hong KongNo answer within 20 s20001 ms, 5 min ago
  • DallasNo answer within 20 s20001 ms, 5 min ago
  • MelbourneReachable6038 ms, 7 min ago
  • MadridReachable2815 ms, 8 min ago
  • TorontoReachable5147 ms, 8 min ago
  • DohaReachable5066 ms, 9 min ago
  • LondonReachable3866 ms, 9 min ago
  • AmsterdamReachable3866 ms, 11 min ago
  • JakartaReachable2329 ms, 12 min ago
  • São PauloReachable2745 ms, 15 min ago
  • Port LouisReachable3638 ms, 24 min ago

We request apua.ag 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.

Outage history

Last problem: 6 Nov, 17:17 UTC, partial outage for 13 min (Could not be loaded from 9 of 34 cities).

Last 9030 days

88.37% of the time without a reported outage, since 5 Nov

Of the last 90 days, 2 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 apua.ag that failed (9,100 checks). Shaded: when our checks showed APUA inet with a problem. Community reports appear separately above, alongside our checks and provider updates.

0%46%91% 00:0006:0012:0018:00 1% of 124 checks failed0% of 100 checks failed50% of 145 checks failed1% of 109 checks failed43% of 148 checks failed0% of 102 checks failed46% of 125 checks failed24% of 131 checks failed19% of 123 checks failed51% of 186 checks failed40% of 136 checks failed25% of 122 checks failed3% of 106 checks failed0% of 108 checks failed23% of 137 checks failed0% of 104 checks failed23% of 132 checks failed0% of 91 checks failed8% of 116 checks failed0% of 105 checks failed13% of 103 checks failed0% of 120 checks failed16% of 118 checks failed46% of 161 checks failed41% of 152 checks failed15% of 131 checks failed27% of 141 checks failed43% of 146 checks failed15% of 106 checks failed0% of 100 checks failed2% of 108 checks failed10% of 120 checks failed11% of 122 checks failed3% of 102 checks failed39% of 145 checks failed30% of 99 checks failed65% of 173 checks failed56% of 177 checks failed55% of 130 checks failed62% of 171 checks failed65% of 136 checks failed3% of 88 checks failed0% of 111 checks failed0% of 104 checks failed16% of 132 checks failed0% of 104 checks failed0% of 106 checks failed7% of 107 checks failed1% of 105 checks failed4% of 100 checks failed2% of 106 checks failed0% of 99 checks failed0% of 103 checks failed28% of 118 checks failed4% of 81 checks failed0% of 81 checks failed0% of 112 checks failed0% of 87 checks failed0% of 99 checks failed10% of 106 checks failed37% of 109 checks failed26% of 85 checks failed3% of 95 checks failed3% of 87 checks failed26% of 110 checks failed13% of 95 checks failed36% of 84 checks failed16% of 43 checks failed2% of 64 checks failed18% of 101 checks failed8% of 85 checks failed24% of 76 checks failed14% of 63 checks failed25% of 93 checks failed65% of 71 checks failed31% of 85 checks failed64% of 81 checks failed91% of 68 checks failed40% of 57 checks failed0% of 83 checks failed0% of 100 checks failed1% of 97 checks failed33% of 82 checks failed27% of 26 checks failed

Recent problems

6 Nov, 17:17 UTCPartial outage13 minCould not be loaded from 9 of 34 cities
6 Nov, 16:58 UTCMajor outage19 minCould not be loaded from 23 of 35 cities
6 Nov, 16:41 UTCPartial outage18 minCould not be loaded from 11 of 35 cities
6 Nov, 12:34 UTCPartial outage13 minCould not be loaded from 15 of 35 cities
6 Nov, 07:48 UTCMajor outage9 minCould not be loaded from 27 of 35 cities
6 Nov, 07:30 UTCMajor outage8 minCould not be loaded from 28 of 35 cities
6 Nov, 07:22 UTCPartial outage8 minCould not be loaded from 12 of 35 cities
6 Nov, 07:03 UTCPartial outage9 minCould not be loaded from 11 of 35 cities
6 Nov, 06:39 UTCMajor outage8 minCould not be loaded from 18 of 35 cities
6 Nov, 06:31 UTCPartial outage8 minCould not be loaded from 12 of 35 cities
What can I try?

Having trouble with APUA inet?

  1. Compare reports from Côte d'Ivoire 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.

Questions about these results

Questions

Is APUA inet down, or is it just me?

Our checks reach APUA inet'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 APUA inet. We load apua.ag 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.

More in Telecom and internet

See the live outage feed for Côte d'Ivoire · Find another service