Text Services logo

Is Text Services Down?

SaaSLive status, outages, and incident history

No. Text Services is up right now.

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

OperationalChecked just nowLive · every 60s

Know the moment Text Services breaks

Text Services 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.

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

Status report

Text Services Status Summary

As of 15:28 UTC on 9 November 2026, Text Services is operational. PulsAPI checked Text Services's official status page and found 8 of 8 components operational, with no active incidents. Over the last 30 days PulsAPI measured 99.96% uptime for Text Services, counting degraded performance as up. The latest incident, "Degraded service: Canned responses, supervision and takeover unavailable", was on Nov 5, 2026 and lasted 24 min.

Cite as: PulsAPI, “Text Services status”, checked 9 November 2026, 15:28 UTC. https://www.pulsapi.com/services/text-services

Text Services Component Status

The main Text Services systems on this page. All 8 are operational right now.

8operational
AI Agents
Operational
API
Operational
Chat Widget
Operational

5 more components tracked

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

Also tracking Integrations, Subprocessors' service, Support on text.com, Text App, Tickets.

See all of them free

Component statuses may change independently during partial outages.

Recent Text Services Outages & Incidents

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

Degraded service: Canned responses, supervision and takeover unavailableResolved Nov 5, 2026 · 24 minResolved

The issue has been resolved, and services are operating normally. No further impact is expected. We’re sorry for any disruption this may have caused and thank you for your patience and understanding. --- [2026-11-05T13:26:13Z] (monitoring) A fix has been implemented, and we are monitoring the results. Some customers may still experience minor disruptions while systems recover. We will share updates if the situation changes. Thank you for your patience. --- [2026-11-05T13:14:53Z] (identified) We identified the problem and the following features are currently unavailable: • Canned responses • Supervising chats • Taking over chats Other features may also load slowly or behave unexpectedly. Our team is working on a fix, and we’ll post updates here as we learn more. --- [2026-11-05T13:12:31Z] (investigating) We’re still investigating the issue affecting canned responses, supervision, and takeover features. Our team is working to find the root cause, and these features remain unavailable. We’ll share another update as soon as we have more information.

Ticketing funcionality not loading Resolved Nov 4, 2026 · 51 minResolved

The issue affecting ticket loading in Text has been fully resolved. Tickets are now loading correctly, and normal service has been restored. --- [2026-11-04T21:42:24Z] (monitoring) The issue affecting ticket loading in Text has been resolved. Our technical team continues to closely monitor the service to ensure tickets load correctly and the application remains stable. --- [2026-11-04T21:18:56Z] (monitoring) The fix for the issue affecting ticket loading in Text has been implemented. Our technical team is currently monitoring the application to ensure that tickets are loading correctly and that normal service has been restored. --- [2026-11-04T21:06:27Z] (investigating) We are currently experiencing an issue that may affect the loading of tickets in Text. Users may encounter difficulties accessing or loading tickets correctly. Our technical team is actively investigating the issue to identify the root cause and restore normal service as soon as possible.

Degraded service: Canned responses, supervision and takeover unavailableResolved Nov 4, 2026 · 1h 9mResolved

This incident has been resolved. Canned responses, supervising and taking over conversations are working normally again for all customers. We’re sorry for the disruption and thank you for your patience. --- [2026-11-04T16:30:13Z] (monitoring) We’ve released a fix for the issue affecting canned responses, supervising and taking over chats. These features should now be working normally again. We’re monitoring the situation closely to make sure everything stays stable. If you’re still having issues, please contact our support team. --- [2026-11-04T16:26:42Z] (identified) We’re still working to fully resolve the issue affecting canned responses, supervising and taking over chats. Our team is applying further fixes and will share another update as soon as we have more information. --- [2026-11-04T16:04:04Z] (identified) We’re continuing to investigate the issue affecting canned responses, supervising and taking over chats. Our team has identified a likely cause and is working on a fix. These features remain unavailable in the meantime. We’ll post another update as soon as we have more information. --- [2026-11-04T15:47:23Z] (investigating) We’re still investigating the issue affecting canned responses, supervision and takeover features. Our team is working to find the root cause, and these features remain unavailable. We’ll share another update as soon as we have more information. --- [2026-11-04T15:27:48Z] (investigating) We’re investigating an issue causing degraded functionality for some customers. The following features are currently unavailable: • Canned responses • Supervising chats • Taking over chats Other features may also load slowly or behave unexpectedly. Our team is working on a fix, and we’ll post updates here as we learn more.

Text Services Uptime History

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

Uptime history91 days observed
Aug 11100.00% average · 11 days with incidentsNov 9

Going further back: Text Services uptime by month and every recorded Text Services outage.

Live Text Services Outage Reports

Problems reported by engineers using Text Services. 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 Text Services problems reported yet.

Something wrong with Text Services on your end?

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

About Text Services

Is Text Services down? Text Services reports live availability for 8 components at status.text.com, among them Support on text.com, Tickets and Subprocessors' service. Track Text Services outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

Over the past 30 days, PulsAPI has measured Text Services uptime at 99.96%. Response times, incident history, and SLA tracking for Text Services are available on the PulsAPI dashboard.

Text Services Status FAQ

Is Text Services down right now?

The verdict at the top of this page comes from the latest poll of the official Text Services 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 Text Services 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 Text Services recovers.

How do I check Text Services uptime history?

PulsAPI tracks Text Services uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.96%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Text Services changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Text Services outages?

PulsAPI reads the official Text Services 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 Text Services components?

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

Can I get alerts when Text Services goes down?

Yes. Create a free account and subscribe to Text Services: 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 Text Services 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 Text Services problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Text Services?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Text Services 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 Text Services with the rest of your stack

2660+ 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