← HonkWatch.com

Is Coins down in Central African Republic?

Coins has problems

People in Central African Republic: 0 reports in the last hour Official page: Partial outage reported, checked 12 min ago Our checks: loads from 35 of 35 places

3 open incidents: Instapay Cashin Maintenance, BAHAMUT Network Maintenance and 1 more2 notices

Partial outage reported by Coins Open incident: Instapay Cashin Maintenance. Going on for 4 d 11 h. Updated 7 Nov, 19:38 UTC, 12 min ago · Official status page
Report a problem
Change country

Known issues (from Coins.ph's status page)

Incidents

  • Instapay Cashin Maintenance (investigating, major impact) Since 29 Sep 2026, 05:00 UTC. Affects InstaPay Cash In · Details Latest update (29 Sep 2026, 05:00 UTC): We are currently investigating this issue.
  • BAHAMUT Network Maintenance (investigating, minor impact) Since 13 Aug 2026, 13:29 UTC. Affects Deposits, Withdrawals · Details Latest update (13 Aug 2026, 13:29 UTC): We regret to inform you that BAHAMUT Network deposits and withdrawals are temporarily unavailable. We apologize for the inconvenience caused. BAHAMUT Network deposits and withdrawals on Coins.ph are undergoing maintenance. However, our other networks are fully functional. We suggest using other bloc
  • C-CASH/PHP Conversion Disabled (investigating) Since 7 Aug 2026, 05:33 UTC · Details Latest update (7 Aug 2026, 05:33 UTC): We regret to inform you that C-CASH/PHP conversion is temporarily unavailable due to an intermittent issue. Our technical team is working on resolving the issue at the earliest possible time. Rest assured that we will provide updates as soon as possible. We appreciate your understanding and apologiz
Show 2 more incidents
  • SWEAT/PHP Conversion Disabled (investigating) Since 12 May 2026, 05:45 UTC · Details Latest update (12 May 2026, 05:45 UTC): We regret to inform you that SWEAT/PHP conversion is temporarily unavailable due to an intermittent issue. Our technical team is working on resolving the issue at the earliest possible time. Rest assured that we will provide updates as soon as possible. We appreciate your understanding and apologize
  • PHPC Redemption (investigating, minor impact) Since 4 Jul 2025, 06:00 UTC · Details Latest update (15 Jul 2025, 02:00 UTC): PHPC deposits and convert selling have been reenabled.

In Coins.ph's own words, as we read them every 15 minutes, last 12 min ago. Read Coins.ph's status page

Reports from people in Central African Republic

Last 24 hours · Central African Republic · times in UTC

0 reports

No community reports in the last 24 hours from Central African Republic. Having trouble? Add your report.

Status page: partial outage, 3 Nov, 08:34 to now 024 00:0006:0012:0018:00 20:00-20:10 UTC: 20 of 20 places loaded it, typical 888 to 1066 ms20:10-20:15 UTC: 35 of 35 places loaded it, typical 885 ms20:15-20:20 UTC: 26 of 26 places loaded it, typical 826 ms20:20-20:30 UTC: 35 of 35 places loaded it, typical 1017 to 1079 ms20:30-20:35 UTC: 33 of 33 places loaded it, typical 1076 ms20:35-20:40 UTC: 35 of 35 places loaded it, typical 954 ms20:40-20:45 UTC: 29 of 29 places loaded it, typical 1169 ms20:45-20:50 UTC: 33 of 33 places loaded it, typical 1130 ms20:50-21:00 UTC: 35 of 35 places loaded it, typical 1053 to 1211 ms21:00-21:05 UTC: 14 of 14 places loaded it, typical 1309 ms21:05-21:10 UTC: 31 of 31 places loaded it, typical 1077 ms21:10-21:15 UTC: 33 of 33 places loaded it, typical 1160 ms21:15-21:20 UTC: 29 of 29 places loaded it, typical 1069 ms21:20-21:25 UTC: 35 of 35 places loaded it, typical 996 ms21:25-21:30 UTC: 14 of 14 places loaded it, typical 948 ms21:30-21:35 UTC: 33 of 33 places loaded it, typical 1355 ms21:35-21:45 UTC: 35 of 35 places loaded it, typical 876 to 1164 ms21:45-21:50 UTC: 20 of 20 places loaded it, typical 916 ms21:50-21:55 UTC: 13 of 13 places loaded it, typical 1552 ms21:55-22:05 UTC: 35 of 35 places loaded it, typical 936 to 1095 ms22:05-22:10 UTC: 22 of 22 places loaded it, typical 830 ms22:10-22:20 UTC: 35 of 35 places loaded it, typical 913 to 1012 ms22:20-22:25 UTC: 32 of 32 places loaded it, typical 1102 ms22:25-22:30 UTC: 26 of 26 places loaded it, typical 1036 ms22:30-23:00 UTC: 35 of 35 places loaded it, typical 942 to 1214 ms23:00-23:05 UTC: 33 of 33 places loaded it, typical 1093 ms23:05-23:10 UTC: 35 of 35 places loaded it, typical 938 ms23:10-23:15 UTC: 33 of 33 places loaded it, typical 1111 ms23:15-23:20 UTC: 34 of 34 places loaded it, typical 979 ms23:20-23:25 UTC: 35 of 35 places loaded it, typical 1205 ms23:25-23:30 UTC: 34 of 34 places loaded it, typical 1115 ms23:30-01:20 UTC: 35 of 35 places loaded it, typical 892 to 1517 ms01:20-01:25 UTC: 34 of 34 places loaded it, typical 898 ms01:25-04:45 UTC: 35 of 35 places loaded it, typical 873 to 1349 ms04:45-04:50 UTC: 34 of 34 places loaded it, typical 876 ms04:50-07:00 UTC: 35 of 35 places loaded it, typical 832 to 1164 ms07:00-07:05 UTC: 34 of 34 places loaded it, typical 1310 ms07:05-09:05 UTC: 35 of 35 places loaded it, typical 850 to 1175 ms09:05-09:15 UTC: 34 of 34 places loaded it, typical 1052 to 1113 ms09:15-09:20 UTC: 24 of 24 places loaded it, typical 1424 ms09:20-10:15 UTC: 35 of 35 places loaded it, typical 888 to 1146 ms10:15-10:20 UTC: 21 of 21 places loaded it, typical 846 ms10:20-10:50 UTC: 35 of 35 places loaded it, typical 845 to 1112 ms10:50-10:55 UTC: 34 of 34 places loaded it, typical 1109 ms10:55-11:35 UTC: 35 of 35 places loaded it, typical 869 to 1153 ms11:35-11:40 UTC: 18 of 18 places loaded it, typical 892 ms11:40-12:05 UTC: 35 of 35 places loaded it, typical 896 to 1243 ms12:05-12:10 UTC: 34 of 34 places loaded it, typical 1119 ms12:10-12:15 UTC: 33 of 33 places loaded it, typical 1143 ms12:15-12:50 UTC: 35 of 35 places loaded it, typical 909 to 1103 ms12:50-12:55 UTC: 33 of 33 places loaded it, typical 1095 ms12:55-13:20 UTC: 35 of 35 places loaded it, typical 840 to 1183 ms13:20-13:25 UTC: 34 of 34 places loaded it, typical 1161 ms13:25-16:45 UTC: 35 of 35 places loaded it, typical 887 to 1199 ms16:45-16:50 UTC: 34 of 34 places loaded it, typical 1058 ms16:50-18:55 UTC: 35 of 35 places loaded it, typical 941 to 1484 ms18:55-19:00 UTC: 34 of 34 places loaded it, typical 1127 ms19:00-19:05 UTC: 35 of 35 places loaded it, typical 1026 ms19:05-19:10 UTC: 30 of 30 places loaded it, typical 1007 ms19:10-19:35 UTC: 35 of 35 places loaded it, typical 912 to 1308 ms19:35-19:40 UTC: 34 of 34 places loaded it, typical 1059 ms19:40-19:50 UTC: 35 of 35 places loaded it, typical 1008 to 1073 ms Typical response time of the places that loaded it, at most 1552 ms

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

Tinted columns: when Coins's status page showed a partial outage, a major outage, as we read it every 15 minutes; the times are when we saw it, not when the provider posted it. Strip under the bars: how many places loaded coins.ph in each 5 minutes, of those that checked, and the line under it their typical response time. Any answer from the website counts as loaded, even an error page. Website checks don't test sign-in, payments or every feature. Tinted columns and our checks are worldwide; the bars count reports from Central African Republic only.

Latest checks, 19:40-19:50 UTC: 35 of 35 places loaded it, typical 1008 to 1073 ms.

Report totals as of 7 Nov, 19:50 UTC

Report a problem with Coins

Choose where you are, then tap what isn't working. Tapping a problem sends your report; no account needed.

What isn't working? Tap one to send

Anonymous · one report per service per hour. This adds your experience to the chart; the provider is not contacted.

Compare worldwide reports · Other services in Central African Republic

Where this status comes from

Provider updates and website checks — Worldwide

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

Our own checks of coins.ph

Every 5 minutes, from our probes

Our checks from 35 cities: all fine.

Tel Aviv: loaded in 937 ms Toronto: loaded in 589 ms London: loaded in 825 ms Port Louis: loaded in 1064 ms Delhi: loaded in 576 ms Santiago: loaded in 863 ms New York: loaded in 1740 ms Johannesburg: loaded in 2347 ms Frankfurt: loaded in 2570 ms Portsmouth: loaded in 2450 ms Madrid: loaded in 782 ms Mumbai: loaded in 1450 ms Sydney: loaded in 967 ms Warsaw: loaded in 1608 ms Seoul: loaded in 542 ms Tokyo: loaded in 709 ms Osaka: loaded in 300 ms Lauterbourg: loaded in 903 ms Dallas: loaded in 1169 ms Los Angeles: loaded in 1008 ms Melbourne: loaded in 816 ms Hamina: loaded in 1712 ms Querétaro: loaded in 734 ms Doha: loaded in 2668 ms Atlanta: loaded in 1106 ms Cape Town: loaded in 1121 ms Amsterdam: loaded in 2291 ms New Jersey: loaded in 2224 ms St. Louis: loaded in 1589 ms São Paulo: loaded in 2014 ms Hong Kong: loaded in 563 ms Bangalore: loaded in 1225 ms Singapore: loaded in 580 ms Jakarta: loaded in 610 ms Seattle: loaded in 822 ms
  • Tel AvivReachable937 ms, just now
  • TorontoReachable589 ms, just now
  • LondonReachable825 ms, just now
  • Port LouisReachable1064 ms, just now
  • DelhiReachable576 ms, just now
  • SantiagoReachable863 ms, just now
  • New YorkReachable1740 ms, just now
  • JohannesburgReachable2347 ms, just now
  • FrankfurtReachable2570 ms, just now
  • PortsmouthReachable2450 ms, just now
  • MadridReachable782 ms, just now
  • MumbaiReachable1450 ms, just now
  • SydneyReachable967 ms, 1 min ago
  • WarsawReachable1608 ms, 1 min ago
  • SeoulReachable542 ms, 1 min ago
  • TokyoReachable709 ms, 1 min ago
  • OsakaReachable300 ms, 2 min ago
  • LauterbourgReachable903 ms, 2 min ago
  • DallasReachable1169 ms, 2 min ago
  • Los AngelesReachable1008 ms, 2 min ago
  • MelbourneReachable816 ms, 2 min ago
  • HaminaReachable1712 ms, 2 min ago
  • QuerétaroReachable734 ms, 2 min ago
  • DohaReachable2668 ms, 2 min ago
  • AtlantaReachable1106 ms, 2 min ago
  • Cape TownReachable1121 ms, 2 min ago
  • AmsterdamReachable2291 ms, 2 min ago
  • New JerseyReachable2224 ms, 2 min ago
  • St. LouisReachable1589 ms, 2 min ago
  • São PauloReachable2014 ms, 2 min ago
  • Hong KongReachable563 ms, 2 min ago
  • BangaloreReachable1225 ms, 2 min ago
  • SingaporeReachable580 ms, 2 min ago
  • JakartaReachable610 ms, 2 min ago
  • SeattleReachable822 ms, 2 min ago

This is separate from the status page: we request coins.ph and note whether it answers. These automated checks do not sign in or use the app's features.

Parts of Coins

Coins.ph

Cash In

  • InstaPay Cash InMaintenance
  • PESONet Cash InMaintenance

Bahamut Network Transfers

  • DepositsMaintenance
  • WithdrawalsMaintenance

149 other parts are working.

Incidents and maintenance

Open incidents

  • Instapay Cashin Maintenance (investigating) Since 29 Sep 2026, 05:00 UTC. Affects InstaPay Cash In · Details
  • BAHAMUT Network Maintenance (investigating) Since 13 Aug 2026, 13:29 UTC. Affects Deposits, Withdrawals · Details
  • C-CASH/PHP Conversion Disabled (investigating) Since 7 Aug 2026, 05:33 UTC · Details
  • SWEAT/PHP Conversion Disabled (investigating) Since 12 May 2026, 05:45 UTC · Details
  • PHPC Redemption (investigating) Since 4 Jul 2025, 06:00 UTC · Details
Outage history

Last 9030 days

0.00% of the time without a reported outage, since 3 Nov

Of the last 90 days, 5 had a partial or major outage, 0 had maintenance only and 85 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

Recent problems

3 Nov, 08:34 UTCPartial outagegoing on, 4 d 11 hOpen incident: Instapay Cashin Maintenance
What can I try?

Having trouble with Coins?

  1. Compare reports from Central African Republic 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 Coins down, or is it just me?

Coins itself reports a problem right now, so it is probably not just you.

How do we know?

We read the official Coins status page and load coins.ph from our own probes in several cities. People can also report problems here. Their reports appear separately and may reveal issues before a provider update.

How often do we check?

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

Other services in Crypto and web3

Each card shows that service's own status, not Coins's. A problem listed here does not mean Coins has one.

See the live outage feed for Central African Republic · Find another service