How to Send Status Page SMS Notifications With Twilio

To send SMS notifications to your status page subscribers, connect a Twilio account to your Hyperping project, then enable the SMS channel on the status page. Twilio sends the texts from a number you own, and bills them to your Twilio account. The whole setup takes about ten minutes, plus a few days of carrier registration if your subscribers are in the US.

I wrote this guide after walking a customer through it. The Hyperping side is short. Most of the waiting happens on the Twilio side, where US carrier rules decide whether your texts are delivered at all. Every screenshot below comes from a real Twilio account and a real Hyperping project, with the account details replaced by placeholders.

Key takeaways

• You need a paid Twilio account, an SMS-capable Twilio number, and a Hyperping plan that includes status page subscribers.
• Hyperping connects with your Account SID, Auth Token and phone number, and checks all three with Twilio before saving.
• US local numbers must be registered under an A2P 10DLC campaign or carriers block the messages. As of September 2026, Twilio charges a $4.50 or $46 one-time brand fee, a $15 campaign verification fee, and $1.50 to $10 per month per campaign.
• A US local number costs $1.15 per month on Twilio, and messages are billed per segment at Twilio's rates. Hyperping adds nothing on top.
• Subscribers get a text for each incident or maintenance update you publish, and when a monitor on the page goes down or comes back up.

What you need before you start

The Twilio connection belongs to the Hyperping project, so every status page in that project sends from the same number.

Step 1: Find your Account SID and Auth Token

Sign in to the Twilio Console and scroll down the home page to the Account Info panel. Copy the Account SID, which starts with AC followed by 32 characters, and the Auth Token, which is hidden until you click Show.

If your company has several Twilio accounts or subaccounts, make sure the account selector at the top of the Console shows the one that owns the number you plan to use. The SID, the token and the number must all belong to the same account.

Step 2: Buy an SMS-capable phone number

Go to Phone Numbers > Manage > Buy a number. Pick the country where most of your subscribers live, tick SMS under Capabilities, and search.

Click Buy next to a number to review it. For a US local number, Twilio shows the monthly fee and flags SMS and MMS with A2P 10DLC registration required. That label is the next step, not an error.

The number then appears under Active numbers. Keep it in E.164 format (+12175550107), which is the format Hyperping asks for.

If you already own a number that sends SMS for another use, you can reuse it. Subscribers will see the same sender for both.

Step 3: Register the number for US messaging

This is the step people skip, and the one that silently breaks delivery. US carriers require every application-to-person message sent from a local number to go through an approved A2P 10DLC campaign. Without it, Twilio accepts the request and the carrier blocks the message. The Console then shows an error like this one:

Open Messaging > Regulatory Compliance > A2P 10DLC Overview to start the registration. Twilio walks you through three stages: a customer profile, a brand, and a campaign.

These are the fees Twilio displayed in September 2026:

For the campaign, describe the real use case: service status notifications sent to people who subscribed on your status page. Sample messages copied from Step 5 below help the review. Once the campaign is approved, add your number to the Messaging Service attached to it.

A toll-free number is the other route for US traffic. It skips 10DLC but needs Twilio's toll-free verification before it can send at volume. Either way, plan a few days of review before your first incident.

Outside the US, check Messaging > Settings > Geo permissions in Twilio: messages to countries that are not enabled there are refused. Some countries have their own sender registration rules, which Twilio documents per country.

Step 4: Connect Twilio in Hyperping

In Hyperping, open Integrations. The Twilio card sits in the Status page section.

Click Connect. The modal offers two paths:

• Proceed sends you to Twilio Connect, which authorizes Hyperping on your Twilio account and buys a new toll-free number for you.
• Use my own credentials instead connects the account and number you prepared in the previous steps.

I recommend your own credentials. You pick the number, you control its registration, and it avoids the Twilio Connect authorization, which can fail on Twilio's side with "Something went wrong, please retry" on the Approve access step.

Paste the Account SID, the Auth Token and the phone number, then click Save.

Before saving anything, Hyperping calls Twilio with those credentials and checks that the account owns the number. If something is off, the form tells you which part:

Once saved, the card shows Enabled and the number your subscribers will receive texts from.

Step 5: Turn on SMS for your status page

Open your status page, then Settings > Notifications. Turn on Subscribe to status page, then the SMS channel under Subscription channels. Email, Slack and Teams can stay on next to it. Publish the page to apply the change.

Visitors now see an SMS tab when they click Get updates on your page. They pick their country, type their number, and receive a confirmation text from your Twilio number.

Subscribe your own phone first and publish a test incident on a private page. It is the fastest way to confirm the whole chain, registration included, before a real outage.

What subscribers receive

Each text starts with your status page name, so subscribers know who is writing. An incident update looks like this:

[Acme status]
Elevated API error rates: investigating status.acme.com/history/...

When a monitor shown on the page changes state, subscribers get a shorter message:

[Acme status]
API: Service Disruption

followed by Service Restored once it recovers. The link in incident texts opens the incident on your status page, where the full update is. For more on who to notify and how often, see the status page subscriber management guide.

How much it costs

Hyperping does not charge for status page SMS. Everything is billed by Twilio to your account:

• Phone number: $1.15 per month for a US local number (September 2026). Toll-free and international numbers have their own prices.
• Messages: billed per segment at Twilio's rate for each destination country. A short status text like the examples above fits in one segment.
• US registration: the one-time A2P 10DLC brand and campaign fees plus the monthly campaign fee listed in Step 3.

The SMS credits included in Hyperping plans are separate. They cover the alerts your own team receives when a monitor goes down, and status page texts never draw from them. See Notification channels for how those work.

Troubleshooting

Subscribers don't receive anything, and Twilio shows error 30034. The number is not registered under an approved A2P 10DLC campaign, or it is not attached to the campaign's Messaging Service. Finish Step 3.

Only some countries receive texts. Enable the missing destinations in Twilio's Geo permissions and check that country's sender rules.

Texts stopped after working for weeks. Check your Twilio balance, and whether someone rotated the Auth Token. Reconnect in Hyperping with the new token.

The SMS tab doesn't show on the status page. The Twilio card must say Enabled in the same project, the SMS channel must be on, and the page must be published after the change.

The Twilio integration docs and the subscribers docs cover the remaining settings. If something still doesn't add up, write to me from the chat in your dashboard and I'll look at your setup.