Outbound Call Failure to a Subset of Hungary Phone Numbers
Final update
Following an amendment to Decree 4/2012 (I.24), calls made to Hungary using fixed or geographic numbers (like +36 1-9...) as a CLI are now likely to be blocked by local carriers, as of October 15, 2025. This will expand to mobile numbers (like +36 20, 30, 70...) starting June 1, 2026. This means calls made with Transit Caller ID and Verified Caller ID will be delivered by Twilio on a best-effort basis when you're using a Hungarian CLI. Recommended steps: - For calls made into Hungary using Verified Caller ID or Transit Caller ID avoid using Hungarian numbers (+36 1-9… and +36 20, 30, 70...) as your CLI as the calls are likely to be blocked. - If a Hungary CLI isn’t a priority for your use case, use a non-Hungarian CLI like your main business or international service number. If you need one, you can quickly get a United States (+1) number right in the Twilio Console to use for these calls. If you observe abnormal failure patterns, please reach out to Twilio Support for further assistance.
Timeline
- Resolved · Oct 30, 21:18 UTC
Following an amendment to Decree 4/2012 (I.24), calls made to Hungary using fixed or geographic numbers (like +36 1-9...) as a CLI are now likely to be blocked by local carriers, as of October 15, 2025. This will expand to mobile numbers (like +36 20, 30, 70...) starting June 1, 2026. This means calls made with Transit Caller ID and Verified Caller ID will be delivered by Twilio on a best-effort basis when you're using a Hungarian CLI. Recommended steps: - For calls made into Hungary using Verified Caller ID or Transit Caller ID avoid using Hungarian numbers (+36 1-9… and +36 20, 30, 70...) as your CLI as the calls are likely to be blocked. - If a Hungary CLI isn’t a priority for your use case, use a non-Hungarian CLI like your main business or international service number. If you need one, you can quickly get a United States (+1) number right in the Twilio Console to use for these calls. If you observe abnormal failure patterns, please reach out to Twilio Support for further assistance.
More from Twilio
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2503:49 UTC | SMS Delivery Delays from Twilio to Claro Brazil | minor | Ongoing |
| Sep 2502:24 UTC | SMS Delivery Delays from a Subset of Twilio Short Codes to Cellularone NE Arizona United States | minor | Ongoing |
| Sep 2420:40 UTC | Event Streams Service Disruption | minor | 5h 44m |
| Sep 2417:55 UTC | SMS Delivery Receipt Delays from a Subset of Twilio Alphanumeric Sender IDs to Ooredoo Algeria | minor | Ongoing |
| Sep 2417:19 UTC | Some Transfer Calls in Elastic SIP Trunking Failing With Error Code 32204 | minor | 43m |
| Sep 2416:22 UTC | Link Branding Creation Fails with HTTP 500 Internal Server Error (Auto SSL Enabled) | minor | 2h 4m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.