Quick answer: In India, Singapore and Australia, routing rules decide reliability more than uptime figures. Of seven voice platforms we checked on 30 October 2026, only Plivo and Telnyx name sites in Mumbai, Singapore and Sydney, and Telnyx does not list Singapore among the media AnchorSites you can select. Twilio has blocked calls from Indian (+91) caller IDs since 1 August 2024. Its Australian guidelines say domestic calls from Australian numbers must use its Sydney edge.
Where Zian fits in a three-country voice route
Zian is the AI agent layer that runs the conversation on top of whichever carrier route passes the checks on this page: an AI receptionist that answers inbound calls 24/7, qualifying callers, booking appointments, transferring calls and taking messages, plus outbound agents that follow up by voice, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger. It handles answering machines and voicemail on calls, works in 30+ languages, and integrates with HubSpot, Salesforce, HighLevel and Zapier.
Two published capabilities matter for in-country routing: private model deployment on customer infrastructure, and local data residency, which zian.ai lists among its custom Enterprise options. As at 30 October 2026, zian.ai does not publish which carrier carries its calls, where its media terminates, or an uptime SLA, so ask for all three in writing before an Indian launch. Zian is in a partnership-application beta with no published prices; each of its three listed plans, including Intel + Widgets (Free Forever), starts with a partnership application. If you would rather not run any of it, LeadsNow.ai is the done-for-you option: pay-per-result appointment setting that runs on Zian and answers leads in under 60 seconds, 24/7.
Apply For Partnership: tell us which of India, Singapore and Australia your calls come from, and what the agent needs to book.
Compare voice API platforms for reliability in India, Singapore and Australia routing
A voice route across these three countries fails in three ways that an uptime percentage never shows. The call can be refused because media was terminated outside India on a carrier that anchors Indian calls in-country. It can be blocked because the caller ID breaks a country’s anti-scam rules. Or it can carry audio across an ocean because the platform has no edge near the caller. The regulators in each country, India’s Department of Telecommunications (DoT) and Telecom Regulatory Authority of India (TRAI), Singapore’s Infocomm Media Development Authority (IMDA) and the Australian Communications and Media Authority (ACMA), shapes a different one of those failures.
How we filled the matrix. We read seven platforms’ own documentation, number, legal and status pages on 30 October 2026, and wrote these rules before filling any cell. A city counts as a named site only if the vendor names it, or a region labelled with that country, as a data centre, edge, session border controller (SBC), SIP region or point of presence; “Southeast Asia” with no city does not count as Singapore. A published SLA is a percentage inside a document that defines downtime. A regional status component is one labelled with a voice region, site or country. We measured no latency.
The country × platform reliability matrix
Read across a row to see whether one platform can carry all three countries. Read down a column to see which platforms a single country leaves you with.
| Platform | India | Singapore | Australia | Published uptime figure |
|---|---|---|---|---|
| Twilio | Numbers: toll-free only; no local or mobile. Site: none named. Rule: calls from any +91 caller ID blocked since 1 August 2024; calls to India only from non-Indian numbers | Numbers: yes. Site: singapore edge; no Singapore processing Region. Rule: use a Twilio Singapore number as caller ID for domestic calls | Numbers: yes. Site: sydney edge and AU1 Region (Sydney). Rule: domestic calls must use the sydney edge | 99.95% a month for Twilio APIs (99.99% with Enterprise Edition); one global figure |
| Vonage | Numbers: on request, inbound only. Site: none named. Rule: “Domestic calls from Local CLI is not supported” | Numbers: on request. Site: Singapore data centre, the APAC default. Rule: domestic calls from Vonage numbers; others “best effort only” | Numbers: landline self-serve, mobile on request. Site: Sydney data centre, the APAC fallback. Rule: invalid caller IDs filtered | Not assessed: vonage.com legal pages returned HTTP 403 |
| Plivo | Numbers: domestic numbers for India-registered businesses only, in India data region accounts, after KYC. Site: Mumbai. Rule: Plivo says media must be anchored in India; violations fail with hangup 4590 | Numbers: local and toll-free. Site: Singapore. Rule: Singapore is not on Plivo’s guaranteed domestic caller ID list | Numbers: local, mobile and toll-free. Site: Sydney. Rule: Australia is on its guaranteed domestic caller ID list | None in its SLA document; its SIP trunking product page cites a “99.99% uptime promise” |
| Telnyx | Numbers: mobile numbers in Mumbai City, Gurugram, Noida and Bangalore with two-way domestic calling, per its India page and 17 September 2026 release note (its 131-country coverage list omits India). Site: Mumbai and Chennai media AnchorSites | Numbers: listed. Site: Singapore named in its APAC footprint in its 29 and 30 September 2026 release notes, but not a selectable media AnchorSite; SIP region “Asia (Beta)”, city not named | Numbers: listed. Site: Australia SIP region; Sydney and Melbourne on its map | None found; its terms say it “cannot guarantee” availability |
| Sinch | Numbers: local and toll-free, inbound only, with business verification. Site: none named | Numbers: local (inbound and outbound) and toll-free. Site: “Southeast Asia” SIP region, city not named | Numbers: local and mobile (inbound and outbound), toll-free. Site: “Australia” SIP region | 99.95% a month, on a “reasonable endeavours” basis, measured per region; its SIP trunking page also advertises a “99.999% SLA managed option” and a “99.95% SLA self-service option” |
| Infobip | Numbers: not confirmed (pricing page renders client-side). Site: an India location on its Regions and data centers page and a Mumbai data centre on its Dedicated connections page, though its SIP trunk SBC table lists no Indian SBC | Numbers: not confirmed. Site: Singapore SBC (and Kuala Lumpur); no published failover pair | Numbers: not confirmed. Site: no Australian SBC in its SBC table | None found; its terms say it cannot guarantee services “will be available to You at all times” |
| Exotel (India only) | Numbers: Exophones in 11 Indian telecom circles. Site: India (IN1) region on its status page | Not assessed | Not assessed | None found in an SLA document; its home page claims “99.99% uptime”; it publishes a status page with incident history |
The matrix in one line: Plivo and Telnyx are the only two naming a site in all three cities, and neither is a clean one-account answer. Telnyx offers numbers in all three countries on one account, Mumbai and Chennai media AnchorSites and Australian sites, but Singapore is not in its AnchorSite list, so you cannot pin Singapore call media to a Singapore AnchorSite, and its Indian numbers need an address in one of four telecom districts. Plivo’s Indian numbers are available only to India-registered businesses, in a separate organisation created in its India data region. For other countries, our comparison of how far each voice API’s number, calling and edge coverage reaches globally counts those lists across seven vendors.
India: why the call has to stay in the country
India is the strictest of the three, and its rules fail a call outright rather than degrading it. Three separate rules apply.
Media anchoring. Plivo’s India documentation says “TRAI regulations require voice traffic for India calls to be anchored on servers located in India”, so your voice-agent platform “must terminate SIP and media on infrastructure in India”; a call that breaks the rule fails with hangup code 4590. That is Plivo’s reading; we did not read a TRAI or DoT instrument that says it in those words. Plivo anchors its side in its Mumbai region, only for organisations created with the India data region, which “cannot be changed after it is created”. It lists LiveKit (region pinning) and ElevenLabs (an India deployment) as able to meet the rule, and not Vapi.
Caller ID from abroad. On 22 October 2024 the DoT launched a system that “identifies and blocks the incoming international calls posing as Indian phone numbers”. The government’s press release says that in its first 24 hours about 1.35 crore calls (roughly 13.5 million), 90% of incoming international calls showing Indian numbers, were identified as spoofed and blocked by telecom service providers. An agent hosted abroad that presents a +91 number is dialling into that filter. Twilio has applied a Do Not Originate block “on all outbound calls from Indian numbers” since 1 August 2024, “whether within India or internationally”, and says calls to India “can only be made from international (non-Indian) numbers”. Vonage says “Domestic calls from Local CLI is not supported”.
Number series for commercial calls. TRAI’s explanatory memorandum to the Telecom Commercial Communications Customer Preference (Third Amendment) Regulations, 2026, dated 18 September 2026, sets out three series:
- 140xx “has already been mandated for promotional calls by all the registered Senders and Telemarketers”.
- 1600xx covers service and transactional calls by banking, financial services and insurance (BFSI) entities, and government-to-citizen calls.
- 1601xx covers service and transactional calls in other sectors. TRAI is introducing it “in a phased manner”, starting with a Direction of 10 August 2026 for utilities, logistics and courier services.
The same memorandum says it may not be desirable to force every small BFSI firm onto 1600 numbers, and the amended regulation lets TRAI classify Senders and exempt some classes. The same regulations define an A2P call as a voice call initiated by an application, software system or automated platform without direct human dialling, including artificial-voice calls, and require every Sender to declare its A2P calls and their caller ID ranges to its originating access provider in advance; an undeclared call is treated as unsolicited commercial communication. Check the commencement clause for when each provision applies. On the provisioning side, Plivo says it currently provisions 140- and 160-series numbers only through Tata Teleservices’ DLT platform, and accepts 140-series provisioning only when the telemarketer entity is registered in Mumbai or Karnataka.
Capacity limits matter too. Plivo’s India data region starts Professional accounts at 2 outbound calls per second and 50 concurrent calls, billed on a 30-second pulse, and Twilio warns that high volumes of short-duration calls “may trigger automated carrier blocks”. For India alone, Exotel says it covers 11 Indian telecom circles, and its status page breaks components out by circle, including Mumbai, Delhi and Karnataka.
The quotable rule for India: on a carrier that anchors Indian calls in India, such as Plivo, an agent whose media cannot terminate inside India has its calls refused before quality matters; the international route that Twilio and Vonage support needs a non-Indian caller ID instead. We compare the agent platforms that speak Indian languages, and how they dial from a registered number, in our guide to agentic voice AI platforms for sales teams in India.
Singapore: the right edge with the wrong caller ID still fails
Five of the seven name a Singapore site: Twilio, Vonage, Plivo, Infobip and Telnyx, though Telnyx names it only in release notes describing its APAC footprint and does not offer it as a media AnchorSite. Sinch runs a Southeast Asia SIP region without naming the city. In Singapore the reliability risk is the caller ID and the recipient’s own settings.
Twilio’s Singapore guidelines say to “use a Twilio Singapore number as the caller ID” for domestic calls, and that verified non-Twilio caller IDs “will no longer be supported in alignment with the measures introduced by IMDA”, under a spoofed-calls code that, in Twilio’s words, “went into effect in 2020”. Vonage says domestic calls from non-Vonage numbers are “best effort only”, though Singapore landline numbers can be ported in.
Then there is the recipient. IMDA’s anti-scam page (last updated 15 May 2026) says all Singapore telcos now offer features to block incoming international calls, and that over 1.1 million subscribers have switched on overseas call blocking. A call that reaches Singapore from an overseas route with a foreign caller ID can therefore be blocked by choice of the person you are calling, however good the carrier’s network is.
Failover is the gap to check. Vonage’s API documentation is the clearest here: its APAC endpoint runs in “Singapore, or Sydney in case of fallback”. Infobip names a Singapore SBC, but the region pairs it publishes for automatic SRV failover cover only Frankfurt–Amsterdam and New York–Portland. Telnyx’s Asia SIP region is labelled Beta as at 30 October 2026. On any of them, ask where a Singapore call goes when the Singapore site is down.
Australia: the Sydney edge and the scam-calls code
Australia and Singapore are the best-served of the three on sites, with five platforms each: in Australia, Twilio, Vonage, Plivo, Telnyx and Sinch all name a Sydney or Australian region. What breaks Australian routes is the industry code on scam calls.
ACMA says it has registered Industry Code C661:2022 Reducing Scam Calls and Scam SMs, which “requires telcos to identify, trace and block SMS scams and scam calls”. ACMA also says “CLI overstamping is legal in Australia”, meaning a business can show an Australian number on a call made from overseas, but that 13, 1300 and 1800 numbers, and invalid or unallocated Australian numbers, “cannot be used for CLI overstamping”. The carriers apply this in their own words:
- Twilio says domestic calls from Australian numbers “must use the sydney edge location in order avoid transiting international gateways”. Calls that do transit an international gateway “may be blocked”. It also blocks anonymous caller IDs and +61 numbers not allocated by ACMA, and treats 13, 1300, 1800 and 1900 numbers as inbound-only.
- Plivo blocks caller IDs beginning +6113, +611300, +611800 and +611900, and lists Australia among the countries where it guarantees domestic caller ID.
- Vonage filters 1300, 1800 and 1900 caller IDs and numbers of the wrong length. Since 24 March 2026, a call whose caller ID is identified as suspected scam activity and blocked at the network level plays a recorded announcement, and Vonage treats those calls as billable.
Twilio adds two practical points. Call forwarding that originates a call using another provider’s number is “protected under the code”. And since Telstra began applying the code, a Telstra-held caller ID used through Twilio to call a Telstra number can be blocked unless the number is ported, which Twilio says “usually takes 4-6 weeks”.
The Region matters as much as the edge. Twilio processes calls in its US1 Region, in the eastern United States, unless you choose otherwise; its AU1 Region in Sydney supports Programmable Voice and Elastic SIP Trunking but not, among other listed features, <Connect><VirtualAgent> or verified caller IDs. Vonage sends calls made through its generic api.nexmo.com address to Virginia by default. Unpinned, an Australian call can enter at Sydney and be processed in the United States.
Published SLAs and status pages for these routes
None of the uptime figures we found is written for a country. Twilio’s API SLA (last updated 9 April 2026) sets one global 99.95% monthly figure and excludes “telecommunications provider-related problems” and outages shorter than five continuous minutes. Sinch’s SLA (version 7.0, 12 January 2024) is the only one that counts unavailability “per region”, from one continuous minute, but on a “reasonable endeavours” basis. Plivo’s SLA document has no percentage. We set out credits and exclusions in our reading of what carriers actually sign in their voice SLAs.
A status page is where regional reliability becomes visible, so check what each one breaks out:
| Platform | Regional voice components on its public status page (read 30 October 2026) | What you can watch for these three countries |
|---|---|---|
| Twilio | AU1 components, including PSTN AU1, Termination AU1, Origination AU1, ConversationRelay AU1 and Media Streams AU1; a “Voice, APAC” component | Australia in detail; Singapore and India only within APAC |
| Vonage | “Voice APAC” | The APAC region as one component |
| Plivo | “Voice, Asia”, “Voice, Oceania”, “SIP Trunking, Asia”, “SIP Trunking, Oceania” | Asia and Oceania separately |
| Telnyx | Site components including Sydney, Melbourne, Mumbai and Chennai; signalling regions including Australia and Asia (Beta) | Australian and Indian sites individually; no Singapore component |
| Sinch | Inbound Calling, Outbound Calling, International Calling and SIP Trunk, not split by region (its messaging components do have an APAC entry) | Voice globally only |
| Infobip | A Voice group with components including India, Singapore and Malaysia; no Australia component | India and Singapore individually |
| Exotel | India (IN1) and per-circle components, including Mumbai, Delhi, Karnataka and Tamil Nadu | India by telecom circle |
An SLA tells you what you can claim after an outage. A regional status component tells you whether the outage is yours, and for a three-country route that is the more useful of the two.
The ACE route check: Anchor, CLI, Edge
The ACE route check runs three tests per country, in this order, because each can fail a call outright before the next matters. Run it separately for India, Singapore and Australia, against the vendor’s own pages.
- Anchor: where does the media terminate? For India, Plivo says both its side and your agent platform must terminate SIP and media in India; on Plivo, that means an organisation created in the India data region. Ask any other carrier whether it applies the same rule. For Australia, pin the application to the in-country Region (Twilio AU1, Vonage api-ap-4), not only the edge. Test: read the debug log of a test call for the processing region and any anchoring hangup code, such as Plivo’s 4590.
- CLI: is this caller ID allowed on this route? India: no +91 caller ID on Twilio and no domestic local caller ID on Vonage; commercial calls use the series TRAI designates. Singapore: a number from the carrier carrying the call. Australia: an ACMA-allocated number held or ported by the originating carrier, never 13, 1300, 1800 or 1900. Test: list every caller ID your agent can present and match each to the table below.
- Edge: what is the nearest named site, and where does it fail over? Name the site per country and its fallback. Vonage publishes Singapore to Sydney; Telnyx says AnchorSite re-routes to the “next closest available site”; elsewhere, ask. Test: get the fallback in writing and allow its addresses through your firewall. Plivo’s allow-list table lists a Sydney block but none for Singapore or Mumbai, so confirm those addresses with Plivo.
Then add the two items that cover the route after launch: subscribe to the status components for each country (table above), and get the uptime figure, exclusions and measurement interval in a signed document rather than from a product page.
| Country | Anchor: pass when | CLI: pass when | Edge: pass when | Regulator to read |
|---|---|---|---|---|
| India | Carrier and agent platform both terminate media in India (Plivo’s stated rule) | No international call presents a +91 number; commercial calls use the TRAI-designated 140xx, 1600xx or 1601xx series | A site in India is named (Plivo Mumbai; Telnyx Mumbai or Chennai; Infobip Mumbai; Exotel IN1) | DoT and TRAI |
| Singapore | Processing region chosen deliberately; no Singapore processing Region exists on Twilio | Domestic calls use a number from the carrier carrying the call; expect overseas caller IDs to be blockable by subscribers | A Singapore site plus a published fallback (Vonage: Singapore to Sydney) | IMDA |
| Australia | Application pinned to an Australian Region (Twilio AU1, Vonage api-ap-4) | ACMA-allocated number held or ported by the originating carrier; no 13, 1300, 1800 or 1900 caller ID | A Sydney or Australian site, and domestic calls never transit an international gateway | ACMA |
Once a route passes, the second-provider build is the same as anywhere else; we walk through it layer by layer in how to build failover into an AI voice agent.
Which option fits which route
This is a decision table, not a carrier ranking. It names the first option to consider for each job, built only on the matrix above.
| Your situation | First option to consider | Why, from the evidence above |
|---|---|---|
| You want calls answered, qualified and booked in all three countries, not a telephony project | Zian (AI agent platform) | Runs inbound reception and outbound follow-up on voice, SMS, email, WhatsApp, Instagram and Messenger, in 30+ languages; ask it which carrier route it uses per country |
| You want the outcome without running any of it | LeadsNow.ai (done-for-you) | Pay-per-result appointment setting that runs on Zian; leads answered in under 60 seconds, 24/7 |
| One carrier account with named sites in Mumbai, Singapore and Sydney | Plivo | Its technical specifications list data centres in all three cities; Telnyx names all three too but offers no Singapore AnchorSite; India still needs an India data region organisation and an India-registered business |
| Australia-heavy traffic with deep regional monitoring | Twilio | Sydney edge, AU1 Region and AU1-level status components; check the AU1 unsupported-feature list first |
| Singapore primary with a published Sydney fallback | Vonage | APAC endpoint runs “Singapore, or Sydney in case of fallback”; numbers there are on request |
| India-only, circle-level coverage | Exotel | Exophones in 11 telecom circles and per-circle status components |
Who each platform is wrong for on these routes
Twilio is the wrong pick if your agent must call Indians from an Indian number: outbound calls from +91 numbers are blocked to every destination, and its only documented Indian numbers are toll-free.
Vonage is the wrong pick if you need instant self-serve numbers in India or Singapore. Both are on request, and its Indian numbers are inbound only.
Plivo is the wrong pick if you want one organisation for all three countries, because Indian numbers need an India data region organisation that cannot be converted later; if your business is not registered in India, because Plivo says only India-registered businesses can rent Indian numbers and use its domestic routes, and others must call over international routes with a non-Indian caller ID; or if you need a contractual uptime percentage, which its SLA document does not give.
Telnyx is the wrong pick if you need Singapore call media anchored in Singapore: its release notes name Singapore in its APAC footprint, but Singapore is not in the AnchorSite list in its developer documentation, and its Asia SIP region is Beta and names no city, as at 30 October 2026. Its Indian numbers cover four telecom districts (Mumbai City, Gurugram, Noida and Bangalore) and need an address in one of them.
Sinch is the wrong pick if you need outbound calls from Indian local numbers (its coverage file marks them inbound only) or a voice status component for Asia-Pacific.
Infobip is the wrong pick if your callers are mainly in Australia, where it names no site, or if you need a published automatic failover pair for Singapore. In India it names a Mumbai data centre, but its SIP trunk SBC table lists no Indian SBC, so confirm which site a SIP trunk would use.
We assessed Exotel for India only. Its docs say it is available in 20 countries, but the page we read does not list them, so confirm Singapore and Australia with Exotel before planning one account for all three.
Apply For Partnership: let Zian answer and book your calls in 30+ languages while you settle the carrier route.
Frequently asked questions
Which voice API has data centres in India, Singapore and Australia?
Of the seven platforms we checked on 30 October 2026, only Plivo and Telnyx name sites in all three cities. Plivo lists data centres in Mumbai, Singapore and Sydney. Telnyx runs Mumbai, Chennai, Sydney and Melbourne media AnchorSites and its release notes name Singapore in its Asia Pacific footprint, but Singapore is not among the AnchorSites you can select. Twilio and Vonage name Singapore and Sydney but nothing in India, and Infobip names Mumbai and Singapore but nothing in Australia.
Can I call Indian numbers from a +91 caller ID through Twilio?
No. Twilio’s help centre says it has applied a Do Not Originate block on all outbound calls from Indian numbers since 1 August 2024, to any destination. Its India voice guidelines say calls to India can only be made from international, non-Indian numbers.
Why do calls to India fail when my AI agent runs outside India?
Plivo’s documentation says TRAI regulations require India call media to be anchored on servers in India, and calls that break the rule fail with hangup code 4590. Separately, a DoT system launched on 22 October 2024 identifies and blocks incoming international calls posing as Indian numbers (PIB press release).
Which caller ID can an AI agent use for calls to Australian numbers?
Use an ACMA-allocated number held or ported by the carrier that originates the call. ACMA says CLI overstamping is legal but cannot use 13, 1300 or 1800 numbers or invalid numbers (ACMA, Caller ID scams), and Twilio says domestic Australian calls must use its Sydney edge.
Why are my calls to Singapore not connecting from an overseas number?
Check the caller ID first. IMDA says every Singapore telco offers international call blocking and over 1.1 million subscribers use it. Twilio and Vonage both expect domestic Singapore calls to use their own Singapore numbers.
Do voice API SLAs cover a specific country?
Not in the documents we read. Twilio’s 99.95% API SLA is one global figure that excludes telecommunications provider problems, and Sinch measures 99.95% per region on a reasonable endeavours basis. Watch the vendor’s regional status components for country-level visibility.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
| 8 public edge locations including sydney and singapore; roaming not available for SIP Domains or Elastic SIP Trunking | Twilio | Edge Locations | 30 October 2026 |
| US1 default Region in the eastern United States | Twilio | Twilio Regions | 30 October 2026 |
| AU1 Region in Sydney; AU1 unsupported features | Twilio | Regional product availability | 30 October 2026 |
| Do Not Originate block on +91 caller IDs since 1 August 2024 | Twilio help centre | Article 57566259695003 | 30 October 2026 |
| No local or mobile India numbers | Twilio help centre | Article 22550748886043 | 30 October 2026 |
| India toll-free numbers reachable only from Indian numbers | Twilio help centre | Article 40728263317915 | 30 October 2026 |
| Calls to India only from non-Indian numbers; short-duration call blocks | Twilio | India voice guidelines | 30 October 2026 |
| Twilio Singapore number for domestic calls; verified non-Twilio caller IDs no longer supported; 2020 spoofed-calls code | Twilio | Singapore voice guidelines | 30 October 2026 |
| Domestic Australian calls via the sydney edge; blocked caller ID types; call forwarding protected | Twilio | Australia voice guidelines | 30 October 2026 |
| Telstra caller ID blocking; porting “usually takes 4-6 weeks” | Twilio help centre | Article 4407966601115 | 30 October 2026 |
| 99.95% (99.99% Enterprise Edition); 5-minute minimum; telecom-provider exclusion | Twilio | Twilio APIs SLA | 30 October 2026 |
| AU1 and Voice, APAC status components | Twilio | status.twilio.com | 30 October 2026 |
| Three geo locations; Singapore with Sydney fallback; api.nexmo.com defaults to Virginia | Vonage | Voice API Regions | 30 October 2026 |
| India: local caller ID not supported; numbers on request, inbound only | Vonage API support | India Voice Features and Restrictions | 30 October 2026 |
| Singapore: non-Vonage numbers “best effort only”; on request | Vonage API support | Singapore Voice Features and Restrictions | 30 October 2026 |
| Australia: caller ID filters; recorded announcement from 24 March 2026, billable | Vonage API support | Australia Voice Features and Restrictions | 30 October 2026 |
| Voice APAC status component | Vonage | Vonage API Status | 30 October 2026 |
| Data centres in Singapore, Sydney and Mumbai; guaranteed domestic caller ID countries; blocked Australian prefixes; allow-list table | Plivo | Zentrunk technical specifications | 30 October 2026 |
| Media anchoring in India; hangup 4590; India data region in Mumbai cannot be changed; platform support | Plivo | Calling in India | 30 October 2026 |
| India KYC documents; India data region only | Plivo | India Number KYC; India number pricing | 30 October 2026 |
| Indian numbers and domestic routes for India-registered businesses only; businesses outside India use international routes with a non-Indian caller ID | Plivo | India Calling Regulations | 30 October 2026 |
| 140-series through Tata DLT; telemarketer registered in Mumbai or Karnataka | Plivo | 140-Series Numbers | 30 October 2026 |
| India data region: 2 outbound calls per second, 50 concurrent calls, 30-second pulse | Plivo | Account Limits | 30 October 2026 |
| Singapore local and toll-free numbers; Australia local, mobile, toll-free | Plivo | Singapore number pricing; Australia number pricing | 30 October 2026 |
| No percentage in SLA document; carrier exclusion | Plivo | Service Level and Support | 30 October 2026 |
| “99.99% uptime promise” product-page figure | Plivo | SIP Trunking | 30 October 2026 |
| Voice and SIP Trunking components for Asia and Oceania | Plivo | Plivo Status | 30 October 2026 |
| SIP regions incl. Australia and Asia (Beta); AnchorSite re-routing | Telnyx | SIP signalling addresses | 30 October 2026 |
| Map pins Sydney, Melbourne, Mumbai, Chennai | Telnyx | Our Network | 30 October 2026 |
| 131 inbound countries and territories; Australia and Singapore listed; India not listed | Telnyx | Global communications | 30 October 2026 |
| Indian mobile numbers in Mumbai City, Gurugram, Noida and Bangalore with two-way domestic calling (17 September 2026); Programmable Voice and Mumbai AnchorSite (16 October 2026) | Telnyx | Telnyx India; India mobile numbers; Programmable Voice in Mumbai | 30 October 2026 |
| Singapore and Sydney named in its APAC footprint (29 and 30 September 2026); AnchorSite list with Mumbai, Chennai and Sydney but no Singapore | Telnyx | Mumbai AnchorSite; Chennai AnchorSite; AnchorSite Configuration | 30 October 2026 |
| “cannot guarantee … availability” | Telnyx | Terms and Conditions of Service | 30 October 2026 |
| Site and signalling-region status components | Telnyx | Telnyx Status | 30 October 2026 |
| Southeast Asia (apse1) and Australia (apse2) SIP regions | Sinch | SIP Trunking | 30 October 2026 |
| India, Singapore, Australia number types and inbound/outbound flags | Sinch (coverage file, June 2026) | Country Coverage | 30 October 2026 |
| 99.95% “reasonable endeavours”; per-region, 1-minute unavailability | Sinch | Messaging, Voice, and Verification SLA | 30 October 2026 |
| “99.999% SLA managed option” and “99.95% SLA self-service option” product-page figures | Sinch | SIP Trunking | 30 October 2026 |
| Voice status components not split by region | Sinch | Sinch Status | 30 October 2026 |
| Singapore and Kuala Lumpur SBCs; SRV failover pairs | Infobip | Set up a SIP trunk | 30 October 2026 |
| India location with local CPaaS processing; Mumbai (Netmagic DC7) and Singapore (Equinix SG1) facilities | Infobip | Regions and data centers; Dedicated connections | 30 October 2026 |
| Cannot guarantee availability “at all times” | Infobip | Service Terms and Conditions | 30 October 2026 |
| Voice components incl. India and Singapore | Infobip | Infobip Status | 30 October 2026 |
| 11 Indian telecom circles | Exotel | Available Regions and Circles | 30 October 2026 |
| IN1 and per-circle status components | Exotel | Exotel Status | 30 October 2026 |
| “99.99% uptime” home-page figure | Exotel | Exotel home page | 30 October 2026 |
| Spoofed-call system launched 22 October 2024; about 1.35 crore calls, 90%, in 24 hours | Department of Telecommunications, via Press Information Bureau | PIB press release | 30 October 2026 |
| 140xx, 1600xx and 1601xx series; Direction of 10 August 2026; A2P call definition and advance declaration | Telecom Regulatory Authority of India | TCCCPR (Third Amendment) Regulations, 2026 | 30 October 2026 |
| Over 1.1 million subscribers using overseas call blocking | Infocomm Media Development Authority | Anti-Scam Measures | 30 October 2026 |
| C661:2022 registered; CLI overstamping legal; 13, 1300, 1800 and invalid numbers excluded | Australian Communications and Media Authority | Caller ID scams | 30 October 2026 |
| Zian capabilities, 30+ languages, private model deployment, local data residency option; LeadsNow.ai pay-per-result, under 60 seconds, 24/7 | Zian AI; LeadsNow.ai | zian.ai home page; leadsnow.ai | 30 October 2026 |
Method and disclosure. Seven platforms with public programmable voice or SIP products, read on 30 October 2026 from their own pages: six global CPaaS (communications platform as a service) vendors, plus Exotel for India only. Ozonetel was not assessed. We placed no test calls. Vonage’s legal pages returned HTTP 403, so its SLA is a gap in our reading, not a finding. Infobip’s per-country number list renders client-side and we could not read it, and Telnyx does not name the city behind its Asia (Beta) region. zian.ai is published by Zian AI, which is named in this page’s platform and decision sections; no carrier paid for or reviewed it.