FireText logo

Is FireText Down?

CommunicationLive status, outages, and incident history

No. FireText is up right now.

Every monitored FireText system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · every 60s

Know the moment FireText breaks

FireText is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official FireText status page
How we know: the official FireText status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

FireText Status Summary

As of 18:44 UTC on 14 November 2026, FireText is operational. PulsAPI checked FireText's official status page and found 6 of 6 components operational, with no active incidents. The latest incident, "Increased Latencies and Timeouts", was on Nov 11, 2026 and lasted 1h 4m.

Cite as: PulsAPI, “FireText status”, checked 14 November 2026, 18:44 UTC. https://www.pulsapi.com/services/firetext

FireText Component Status

The main FireText systems on this page. All 6 are operational right now.

6operational
API
Operational
Application
Operational
Inbound SMS
Operational

3 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Outbound SMS, URL Shortener, Website.

See all of them free

Component statuses may change independently during partial outages.

Recent FireText Outages & Incidents

Incident history from the official FireText status page, including resolution updates.

Increased Latencies and TimeoutsResolved Nov 11, 2026 · 1h 4mResolved

This incident has been resolved. --- [2026-11-11T16:19:35.784+00:00] (monitoring) During observations for the delayed receipts. The team noted increased i/o latencies at times to service requests on one of our databases going back to 5am. This will have resulted in increased response times periodically to APP and API requests. At 15:21 GMT requests were failed over to a different instance. Services appear to be operating as normal, the team will continue to monitor performance over the next hour before closing the incident. We apologise for any inconvience caused.

Delayed Delivery ReceiptsResolved Nov 11, 2026 · 4h 44mResolved

This incident has been resolved. --- [2026-11-11T12:55:08.627+00:00] (monitoring) Between 11/11/26 09:00 - 10:00 GMT the processing of some delivery receipts appear to have been delayed, brief recurrences were observed. A fix has been applied as of 12:00 GMT and processing appears to stable. The team will continue to monitor for the next hour to ensure there is no recurrence.

O2 degradation of MT, MO and DR deliveryResolved Oct 22, 2026 · 2h 16mResolved

This incident was resolved at 22/10/26 15:16 BST. --- [2026-10-22T13:56:58.658+01:00] (investigating) 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.

FireText Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a FireText incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live FireText Outage Reports

Problems reported by engineers using FireText. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No FireText problems reported yet.

Something wrong with FireText on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About FireText

FireText posts its status at status.firetext.co.uk. The page covers 6 components, among them API, Application and Inbound SMS. Past incidents and uptime for FireText stay on this page, which helps when you want to know how often it has trouble.

FireText Status FAQ

Is FireText down right now?

The verdict at the top of this page comes from the latest poll of the official FireText status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if FireText is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until FireText recovers.

How do I check FireText uptime history?

PulsAPI tracks FireText uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever FireText changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect FireText outages?

PulsAPI reads the official FireText status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual FireText components?

Yes. PulsAPI monitors 6 individual FireText components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when FireText goes down?

Yes. Create a free account and subscribe to FireText: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with FireText to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot FireText problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor FireText?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so FireText plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track FireText with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services