الحالة

حالة النظام

الحالة المباشرة للواجهة البرمجية ولوحة التحكم ومعالجة المدفوعات ومجموعة المشغّلين.

جميع الأنظمة تعمل

لا يوجد عطل جارٍ. الـ API ولوحة التحكم ومعالجة المدفوعات وتسليم الرسائل وتسليم webhooks تستجيب جميعها بشكل طبيعي.

فُحصت ٠٩:١٤ UTC

إجمالي مدة التشغيل، آخر 90 يومًا

99.96 %

المكوّنات

  • واجهة REST API
    تعمل
    قبل 90 يومًاالتوافر خلال 90 يومًا · 99.98 %اليوم

    وسيط زمن استجابة الواجهة 74 ms

  • لوحة التحكم
    تعمل
    قبل 90 يومًاالتوافر خلال 90 يومًا · 99.99 %اليوم

    وسيط زمن استجابة الواجهة 168 ms

  • المدفوعات (OxaPay)
    تعمل
    قبل 90 يومًاالتوافر خلال 90 يومًا · 99.94 %اليوم

    وسيط زمن استجابة الواجهة 240 ms

  • تسليم الرسائل
    تعمل
    قبل 90 يومًاالتوافر خلال 90 يومًا · 99.91 %اليوم
  • تسليم Webhooks
    تعمل
    قبل 90 يومًاالتوافر خلال 90 يومًا · 99.96 %اليوم

    وسيط زمن استجابة الواجهة 96 ms

كل الأوقات بتوقيت UTC. وتُقاس مدة التشغيل لكل مكوّن، مرجَّحة بحصة حركة البيانات المتأثرة.

سجل الأعطال

يُعلَن عن نوافذ الصيانة هنا قبل 48 ساعة على الأقل.

اطلب من الدعم إضافتك

يوليو ٢٠٢٦

أداء متراجعتم الحل

Webhook deliveries failing to endpoints behind one certificate chain

المتأثر
تسليم Webhooks
المدة
٠٨:٥٢–١١:١٨ UTC · 2 ساعة 26 دقيقة
  1. ٠٨:٥٢ UTC

    Webhook deliveries to a subset of endpoints are failing with a TLS verification error. Events are queued and will be retried, so nothing is being dropped. Investigating.

  2. ٠٩:١٤ UTC

    A base image update on the delivery workers shipped a trust store that no longer carries a cross-signed intermediate that several customer endpoints still serve. Around 4 % of registered endpoints are affected.

  3. ٠٩:٤٨ UTC

    We have pinned the previous trust store on the delivery workers and the queued deliveries are going out. The oldest queued event is 56 minutes old.

  4. ١١:١٨ UTC

    Resolved. The queue is empty and every event from the window was delivered well inside the 24-hour retry budget. The trust store is now pinned explicitly and updated deliberately instead of being inherited from the base image.

انقطاع جزئيتم الحل

Balance credits delayed by a payment callback backlog

المتأثر
المدفوعات (OxaPay)
المدة
١١:٠٦–١٢:٢٤ UTC · 1 ساعة 18 دقيقة
  1. ١١:٠٦ UTC

    Top-up credits are arriving late. Payments are being received and recorded, and no funds are at risk, but balances are updating with a delay. Investigating.

  2. ١١:٢١ UTC

    OxaPay moved their callback traffic to a new source range this morning. Our allowlist rejected it, so callbacks were retried instead of accepted. About 340 callbacks are pending.

  3. ١١:٤٤ UTC

    The new range is allowlisted and the retries are being accepted. The backlog is draining oldest first at roughly 90 callbacks a minute.

  4. ١٢:٢٤ UTC

    Resolved. Every pending credit has been applied and the longest delay was 78 minutes. We have asked to be notified of source-range changes in advance, and we now alert on a callback rejection rate above 1 % rather than only on queue depth.

يونيو ٢٠٢٦

صيانةتم الحل

Singapore maintenance window overran

المتأثر
واجهة REST API, لوحة التحكم
المدة
١٨:٠٠–١٨:٤٧ UTC · 47 دقيقة
  1. ١٨:٠٠ UTC

    Maintenance window open, as announced on 2026-06-05. The Singapore entry point is draining and requests are being served from Frankfurt for the duration.

  2. ١٨:١٢ UTC

    The kernel upgrade is finished but one node is not rejoining the load balancer. Singapore stays drained while we look at it. Frankfurt is serving all traffic and latency from Asia is elevated to roughly 300 ms.

  3. ١٨:٣١ UTC

    The node was presenting a certificate issued before the upgrade. It has been reissued and the node is back in rotation.

  4. ١٨:٤٧ UTC

    Resolved. Singapore is serving again at normal latency. We announced a 20-minute window and the drain lasted 47 minutes, which we should have said here sooner than we did.

انقطاع جزئيتم الحل

Inbound SMS dropped on an Indonesian operator

المتأثر
تسليم الرسائل, تسليم Webhooks
المدة
٠٥:٤٤–١٢:٢٦ UTC · 6 ساعة 42 دقيقة
  1. ٠٥:٤٤ UTC

    Activations on Indonesian numbers have been expiring without a code at a much higher rate than normal since about 05:10. Purchases and the rest of the catalogue are unaffected.

  2. ٠٦:٣٠ UTC

    The operator changed the route for inbound international SMS overnight without notice. Messages reach their network and are not forwarded to us. The affected ranges are out of routing as of 06:24.

  3. ٠٧:٠٥ UTC

    Indonesia is now served entirely by the two remaining operators. Success rate is 88 % against 93 % normally, and stock is about a third lower. Webhook volume for Indonesia is down accordingly.

  4. ٠٩:٤٠ UTC

    The operator has acknowledged the route change and is reverting it. We will not return the ranges to routing until our own probes have delivered cleanly for two hours.

  5. ١٢:٢٦ UTC

    Resolved. The ranges are back in routing and delivering normally. 1,946 activations expired without a code during the incident; every one of them was refunded in full, automatically, with no ticket required.

مارس ٢٠٢٦

أداء متراجعتم الحل

Rate limiter rejecting requests that were inside their budget

المتأثر
واجهة REST API
المدة
٠٧:٢٩–٠٩:١١ UTC · 1 ساعة 42 دقيقة
  1. ٠٧:٢٩ UTC

    A number of API keys are receiving 429 responses while comfortably inside their per-minute budget. Investigating.

  2. ٠٧:٤٨ UTC

    A counter shard lost its expiry during a cache node replacement overnight, so counts from the previous hour were never cleared for keys hashed onto that shard. Roughly 6 % of keys are affected.

  3. ٠٨:١٥ UTC

    The affected shard has been flushed and the keys on it are being served normally. We are checking the remaining shards for the same condition.

  4. ٠٩:١١ UTC

    Resolved. Counters now carry an absolute expiry written at creation instead of one set after the first increment, so a node replacement cannot leave a counter without one. No account was charged for a request that was rejected.

يناير ٢٠٢٦

انقطاع جزئيتم الحل

Top-up invoice creation failing upstream

المتأثر
المدفوعات (OxaPay)
المدة
١٠:٢٢–١٣:٠٥ UTC · 2 ساعة 43 دقيقة
  1. ١٠:٢٢ UTC

    Creating a top-up invoice is failing with an upstream error for most currencies. Invoices already created are unaffected and payments already sent are being credited normally.

  2. ١٠:٤٠ UTC

    OxaPay has confirmed an incident on their invoice API. Purchases, activations, rentals and the rest of the API are not affected; only creating a new top-up is.

  3. ١١:٣٥ UTC

    Partial recovery upstream. USDT-TRC20 and TON invoices are being created again. BTC and ETH still fail intermittently.

  4. ١٢:٤١ UTC

    All currencies are creating invoices again. We are keeping this open while we watch the error rate.

  5. ١٣:٠٥ UTC

    Resolved. 214 invoice attempts failed during the window and none of them took a payment. The top-up page now names the specific currency that is unavailable instead of failing generically.

نوفمبر ٢٠٢٥

انقطاع جزئيتم الحل

Dashboard failed to load after a deploy

المتأثر
لوحة التحكم
المدة
١٥:٣٨–١٦:١٩ UTC · 41 دقيقة
  1. ١٥:٣٨ UTC

    The dashboard is failing to load for some visitors with a chunk loading error. The API is unaffected, so automations are still running normally.

  2. ١٥:٤٧ UTC

    A deploy at 15:31 invalidated the asset manifest while open sessions were still holding the previous one. Anyone who had the dashboard open before the deploy is affected; a hard reload works around it.

  3. ١٦:٠٢ UTC

    The previous asset bundle has been re-published alongside the new one so both manifests resolve. Error reports have stopped.

  4. ١٦:١٩ UTC

    Resolved. Old asset bundles are now retained for 24 hours after a deploy, and the client reloads itself once when it sees a manifest it does not recognise.

أكتوبر ٢٠٢٥

انقطاع جزئيتم الحل

Upstream operator degraded in Brazil

المتأثر
تسليم الرسائل
المدة
٠٩:١٥–١٧:٤٨ UTC · 8 ساعة 33 دقيقة
  1. ٠٩:١٥ UTC

    Success rates on Brazilian numbers have fallen from 91 % to about 44 % since 08:30. Purchases still succeed, but a large share of activations are expiring without a code.

  2. ٠٩:٥٢ UTC

    One operator range is being rejected by several services at once, which normally means the range has been flagged rather than that delivery is broken. Its pool score is set to zero so routing avoids it.

  3. ١١:١٠ UTC

    Brazilian success rate is back to 86 % on the remaining operators. Stock for Brazil is roughly 40 % below normal while the flagged range is excluded.

  4. ١٤:٣٠ UTC

    The operator confirms the range was flagged by a downstream aggregator and is migrating the block. We are keeping it out of routing until our own probes show it recovering.

  5. ١٧:٤٨ UTC

    Resolved. Brazil is at 90 % success on a reduced pool. Every activation that expired during the incident was refunded automatically. The flagged range stays out of routing until the migration is finished.

أغسطس ٢٠٢٥

انقطاع كبيرتم الحل

Primary database failover

المتأثر
واجهة REST API, لوحة التحكم, المدفوعات (OxaPay), تسليم Webhooks
المدة
٠٤:٠٧–٠٤:٥٢ UTC · 45 دقيقة
  1. ٠٤:٠٧ UTC

    The API is returning 500 for most requests and the dashboard will not load. The primary database is not responding. Investigating at the highest priority.

  2. ٠٤:١٤ UTC

    The primary lost its storage volume. Automatic failover did not trigger because the primary was still answering health checks on its keepalive port. We are promoting the standby manually.

  3. ٠٤:٢٦ UTC

    The standby is promoted and the API is answering again. Error rate is back to baseline. We are now verifying whether any committed purchase was lost in the promotion.

  4. ٠٤:٥٢ UTC

    Resolved. 26 seconds of writes were lost in the promotion, covering 11 purchases. All 11 were refunded in full and the accounts were emailed individually. Health checks now run a real query instead of probing the keepalive port, and failover is exercised weekly.

يونيو ٢٠٢٥

صيانةتم الحل

Scheduled maintenance: PostgreSQL major version upgrade

المتأثر
واجهة REST API, لوحة التحكم, المدفوعات (OxaPay), تسليم Webhooks
المدة
٠٢:٠٠–٠٢:٤١ UTC · 41 دقيقة
  1. ٠٢:٠٠ UTC

    Maintenance window open, as announced on 2025-06-10. Writes return 503 with a Retry-After header; reads and long-polls continue to be served from the replica.

  2. ٠٢:١٨ UTC

    The upgrade is complete and the primary is accepting writes. We are comparing query plans against the pre-upgrade baseline before calling this done.

  3. ٠٢:٤١ UTC

    Resolved. Total write unavailability was 18 minutes, inside the 45-minute window we announced. Activations that were open during the window were extended by 18 minutes so that no one lost part of an activation to the maintenance.

أبريل ٢٠٢٥

انقطاع جزئيتم الحل

Balance credits delayed by a stalled payment consumer

المتأثر
المدفوعات (OxaPay)
المدة
١٨:٤١–٢١:٠٥ UTC · 2 ساعة 24 دقيقة
  1. ١٨:٤١ UTC

    Top-ups paid in the last half hour are not appearing on balances. Payments are being received and recorded; it is the credit step that is backed up. No funds are at risk.

  2. ١٩:٠٢ UTC

    The consumer that applies OxaPay callbacks to balances stopped acknowledging messages after a deploy at 18:10, and the queue has grown to about 400 callbacks. We are rolling that deploy back.

  3. ١٩:٣٥ UTC

    The rollback is live and the backlog is draining at roughly 60 callbacks a minute. The oldest pending credit is 51 minutes old.

  4. ٢٠:٢٠ UTC

    Backlog cleared. Every payment received during the incident has been credited, including four invoices that expired while their callback was waiting.

  5. ٢١:٠٥ UTC

    Resolved. The deploy removed the acknowledgement path for a callback that arrives for an invoice already in a terminal state, so those callbacks were retried forever and blocked the queue behind them. They are now acknowledged and logged.

مارس ٢٠٢٥

أداء متراجعتم الحل

Elevated SMS delivery times on Indian ranges

المتأثر
تسليم الرسائل
المدة
٠٦:٥٢–١٠:٣٤ UTC · 3 ساعة 42 دقيقة
  1. ٠٦:٥٢ UTC

    Delivery times for Indian numbers are running above 60 seconds against a normal median of 9. Numbers are still being issued and the refund window is unchanged. Investigating.

  2. ٠٧:٢٠ UTC

    One of our two Indian upstreams is queueing inbound SMS at its own gateway. India is being routed to the second provider while we wait on their side.

  3. ٠٨:٠٥ UTC

    The shift is complete and new Indian activations are delivering at a median of 14 seconds. Activations bought before 07:20 that are still open will either deliver or auto-refund at the end of their window.

  4. ٠٩:٤٠ UTC

    The upstream has drained its queue and reports a full disk on a gateway node as the cause. We are keeping traffic on the second provider until their median has been stable for an hour.

  5. ١٠:٣٤ UTC

    Resolved. India is back on both providers at a median of 9.2 seconds. 812 activations expired without a code during the incident and were refunded automatically.

تلقَّ الإشعارات

تغيّرات الحالة عبر البريد الإلكتروني أو Webhook.

اشترك في تغذية RSS