Skip to content
Back to XenditIncident Postmortem
Xendit logo

Xendit

Tracked by PulseWatch

Auto-drafted postmortem

Xendit outage on August 14 — 5h 47m disruption

Aug 14, 06:39 AM → Aug 14, 12:27 PM · 5h 47m · medium

Xendit experienced a service disruption on August 14, which was initially detected through user reports. The incident began at 06:39 UTC and was fully resolved by 12:27 UTC on the same day.

Peak reports
4
in 15 min
Total reports
88
during the incident
Duration
5h 47m
tracked by PulseWatch

Impact

During the disruption, users primarily reported issues related to API functionality. A total of 88 user reports were received, with a peak of 4 reports within a 15-minute period. No specific regional impact was recorded during this incident. The disruption was correlated across official/vendor signals, confirming the widespread nature of the reported API issues.

Top reported issues

  • API issues88

Incident timeline

  1. Aug 14, 06:39 AM

    PulseWatch detected elevated report volume (medium severity)

  2. Aug 14, 06:45 AM

    Peak of 4 reports in 15 minutes (baseline 1.3)

  3. Aug 14, 07:27 AM

    Status updated: major issue

  4. Aug 14, 07:33 AM

    Status updated: major issue

  5. Aug 14, 07:36 AM

    Status updated: major issue

  6. Aug 14, 07:42 AM

    Status updated: major issue

  7. Aug 14, 07:57 AM

    Status updated: possible issue

  8. Aug 14, 08:03 AM

    Status updated: major issue

  9. Aug 14, 08:06 AM

    Status updated: possible issue

  10. Aug 14, 08:12 AM

    Status updated: possible issue

  11. Aug 14, 08:24 AM

    Status updated: major issue

  12. Aug 14, 08:29 AM

    Status updated: possible issue

  13. Aug 14, 08:34 AM

    Status updated: major issue

  14. Aug 14, 08:36 AM

    Status updated: possible issue

  15. Aug 14, 08:42 AM

    Status updated: possible issue

  16. Aug 14, 08:53 AM

    Status updated: major issue

  17. Aug 14, 08:57 AM

    Status updated: possible issue

  18. Aug 14, 09:03 AM

    Status updated: major issue

  19. Aug 14, 09:06 AM

    Status updated: possible issue

  20. Aug 14, 09:12 AM

    Status updated: possible issue

  21. Aug 14, 09:23 AM

    Status updated: major issue

  22. Aug 14, 09:27 AM

    Status updated: possible issue

  23. Aug 14, 09:33 AM

    Status updated: major issue

  24. Aug 14, 09:37 AM

    Status updated: possible issue

  25. Aug 14, 09:42 AM

    Status updated: possible issue

  26. Aug 14, 09:53 AM

    Status updated: major issue

  27. Aug 14, 09:56 AM

    Status updated: possible issue

  28. Aug 14, 10:03 AM

    Status updated: major issue

  29. Aug 14, 10:06 AM

    Status updated: possible issue

  30. Aug 14, 10:11 AM

    Status updated: possible issue

  31. Aug 14, 10:23 AM

    Status updated: major issue

  32. Aug 14, 10:26 AM

    Status updated: possible issue

  33. Aug 14, 10:33 AM

    Status updated: major issue

  34. Aug 14, 10:36 AM

    Status updated: possible issue

  35. Aug 14, 10:41 AM

    Status updated: possible issue

  36. Aug 14, 10:53 AM

    Status updated: major issue

  37. Aug 14, 10:57 AM

    Status updated: possible issue

  38. Aug 14, 11:03 AM

    Status updated: major issue

  39. Aug 14, 11:07 AM

    Status updated: possible issue

  40. Aug 14, 11:11 AM

    Status updated: possible issue

  41. Aug 14, 11:23 AM

    Status updated: major issue

  42. Aug 14, 11:26 AM

    Status updated: possible issue

  43. Aug 14, 11:33 AM

    Status updated: major issue

  44. Aug 14, 11:36 AM

    Status updated: possible issue

  45. Aug 14, 11:41 AM

    Status updated: possible issue

  46. Aug 14, 11:53 AM

    Status updated: major issue

  47. Aug 14, 11:58 AM

    Status updated: possible issue

  48. Aug 14, 12:04 PM

    Status updated: major issue

  49. Aug 14, 12:06 PM

    Status updated: possible issue

  50. Aug 14, 12:12 PM

    Status updated: possible issue

  51. Aug 14, 12:27 PM

    Report volume returned to baseline — incident resolved

Official updates

  1. Aug 14, 06:39 AM

    Xendit status page acknowledged the incident.

    View official source
Draft auto-generated by PulseWatch when the incident resolved. Based on aggregated user-report signals and the sources listed above.
This postmortem was auto-generated from PulseWatch's record of the incident. · Model: gemini-2.5-flash