Is Firetext down?

Last checked just now
Current status
Firetext is up

No incidents right now.

Firetext is operational right now. Last checked just now; the most recent incident resolved 7d ago.

Real-time Firetext status, recent outages, and incident history: pulled directly from Firetext's official status page at status.firetext.co.uk every 5 minutes. Pingoru tracks 6 Firetext services and has captured 4 incidents in the last 90 days (97.04% uptime). Get email, Slack, Discord, or webhook alerts the moment Firetext reports a new incident, free for 3 monitors, no credit card.

Users who monitor Firetext also follow these Marketing services: Mailgun Klaviyo Iterable Braze Brevo Customer.io ZoomInfo Optimizely SurveyMonkey Yotpo View all 8,000+ providers
Firetext uptime 97.04% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 2h 16m
    Started Oct 22, 2026, 12:56 PM UTC · Resolved Oct 22, 2026, 03:13 PM UTC
    Outbound SMSInbound SMS
    Timeline · 2 updates
    • investigating · Oct 22, 2026, 12:56 PM UTC

      We are aware of some degradation with SMS performance to and from O2 starting at 22/10/26 13:28 BST. MT, MO and DR deliveries maybe affected or delayed.

    • resolved · Oct 22, 2026, 03:13 PM UTC

      This incident was resolved at 22/10/26 15:16 BST.

    Latest: This incident was resolved at 22/10/26 15:16 BST.

  2. Resolved 22h 43m
    Started Aug 18, 2026, 11:47 PM UTC · Resolved Aug 19, 2026, 10:31 PM UTC
    APIApplicationOutbound SMSInbound SMSURL ShortenerWebsite
    Timeline · 9 updates
    • investigating · Aug 18, 2026, 11:47 PM UTC

      We are aware of services currently being unavailable. The team is actively investigating and working to resolve the issues.

    • investigating · Aug 19, 2026, 12:20 AM UTC

      Our database instances have crashed as 19/08/26 23:47 BST. The team is currently looking to restore services from backups but we anticipate this to take several hours. Outbound and Inbound SMS are currently affected.

    • investigating · Aug 19, 2026, 12:23 AM UTC

      Our database instances have crashed as 18/08/26 23:47 BST. The team is currently looking to restore services from backups but we anticipate this to take several hours. Outbound and Inbound SMS are currently affected.

    • investigating · Aug 19, 2026, 12:24 AM UTC

      Our database instances have crashed as 18/08/26 23:47 BST. The team is currently looking to restore services from backups but we anticipate this to take several hours. Outbound and Inbound SMS are currently affected.

    • investigating · Aug 19, 2026, 03:57 AM UTC

      Attempts to restore services are taking longer than expected. We apologise for the continued interruption.

    • investigating · Aug 19, 2026, 07:41 AM UTC

      Unfortunately restorations of the affected database instances are still in progress, we're awaiting feedback from engineers on expediting the process. A further update will be provided at 10am.

    • investigating · Aug 19, 2026, 09:03 AM UTC

      Progress is still slow but approaching 50%, the team continue to evaluate all available options. Next update by 12pm.

    • monitoring · Aug 19, 2026, 11:11 AM UTC

      A fix was put in place promoting a new instance around 11:30. Messages look to be flowing again. The team will continue to monitor before closing the incident. If still having any issues do let us know.

    • resolved · Aug 19, 2026, 10:31 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 1h 15m
    Started Aug 14, 2026, 10:01 AM UTC · Resolved Aug 14, 2026, 11:17 AM UTC
    Outbound SMSInbound SMS
    Timeline · 2 updates
    • investigating · Aug 14, 2026, 10:01 AM UTC

      We are aware of some degradation with SMS performance to and from O2 starting at 14/08/26 10:36 BST. MT, MO and DR deliveries maybe affected or delayed.

    • resolved · Aug 14, 2026, 11:17 AM UTC

      This incident has been resolved as of 14/08/26 11:12 BST.

    Latest: This incident has been resolved as of 14/08/26 11:12 BST.

Incident record

Since April 2026 · Statuspage by Atlassian · 6 components checked every 5 minutes
51incidents recorded
13last 12 months
3last 90 days
10 hourstypical duration, 12 months

The longest incident in the last year, Hosting Provider Connectivity on May 11, 2026, ran for 25 hours. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Inbound SMS11
  • Outbound SMS11
  • URL Shortener5
  • API4
  • Application4

Latest incidents

  • O2 degradation of MT, MO and DR delivery October 22, 2026 · 2 hours · degraded service

    We are aware of some degradation with SMS performance to and from O2 starting at 22/10/26 13:28 BST. MT, MO and DR deliveries maybe affected or delayed.

  • Unplanned Outage August 18, 2026 · 23 hours · major outage

    We are aware of services currently being unavailable. The team is actively investigating and working to resolve the issues.

  • O2 degradation of MT, MO and DR delivery August 14, 2026 · 75 minutes · degraded service

    We are aware of some degradation with SMS performance to and from O2 starting at 14/08/26 10:36 BST. MT, MO and DR deliveries maybe affected or delayed.

Outage history

Past 90 days · 3 incidents View full outage history →