Fomo Outage History

Fomo is up right now

Pingoru has recorded 11 incidents for Fomo: 0 in the last 12 months and 0 in the last 90 days.

Source: status.fomopay.com

11incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Fomo in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 509 (0%)

Incidents, newest first

Notice June 24, 2025 PayNow transaction affected –

Started Jun 24, 2025, 03:00 PM UTC· resolved Jun 24, 2025, 03:00 PM UTC

  1. resolved Jun 25, 2025, 01:45 AM UTC

    We are aware of an issue where some of the PayNow transactions via one of our bank partners are not showing as paid since 24 JUN 2025 22:52 (SGT). Our bank partner has resolved the issue on the same day at 23:22 (SGT).

Read the full incident report →

Minor March 26, 2025 PayNow transactions affected 12h 52m ipg.fomopay.net, pos.fomopay.net

Started Mar 26, 2025, 05:00 PM UTC· resolved Mar 27, 2025, 05:53 AM UTC

  1. investigating Mar 27, 2025, 04:57 AM UTC

    We are aware of an issue where some of the PayNow transactions via one of our bank partners are not showing as paid.

  2. identified Mar 27, 2025, 04:58 AM UTC

    Our bank partner is working on this issue.

  3. identified Mar 27, 2025, 04:58 AM UTC

    Our bank partner has informed us that the system is currently being restored. Some transactions are already being processed, and they will provide further updates once everything is fully confirmed and clear.

  4. monitoring Mar 27, 2025, 04:59 AM UTC

    Our bank partner has confirmed that the system has been fully recovered. We will continue to monitor the situation to ensure everything remains stable.

  5. resolved Mar 27, 2025, 05:53 AM UTC

    This incident has been resolved.

Read the full incident report →