Ecuador DNS Propagation Checker
Run a DNS lookup against 6 resolvers located in Ecuador — Quito · Portoviejo · Quito · Ambato · Quito · Ambato.
- Resolved
- No answer
- Checking
-
Quito
Ecuador
—
-
Portoviejo
Ecuador
—
-
Quito
Ecuador
—
-
Ambato
Ecuador
—
-
Quito
Ecuador
—
-
Ambato
Ecuador
—
What checking DNS from Ecuador tells you
A DNS resolver keeps a cached copy of each record for as long as its time-to-live allows, and does so separately in every location. A change you have published can be live on one resolver while another still serves the old answer.
Checking from Ecuador looks up the record on servers inside the country, so you see what people there actually get rather than what a resolver on another continent returns.
This matters most right after you edit a record: an update visible on a global resolver like 8.8.8.8 can still be stale at a local ISP in Ecuador until its cached copy expires. The check confirms the new value has reached the resolvers your Ecuador visitors depend on.
On the evening of March 28, 2014, Google and YouTube went dark across Ecuador. The outage came not from a routing fault but from AEPROVI, the association that runs the country's two exchange points, which briefly cut the sites off at the government's request. It was a rare glimpse of a quieter setup: AEPROVI has held a cooperation agreement with the state telecoms regulator since 2012, and the method it uses to block domains has never been published.
Almost every Ecuadorian connection runs through a few operators — Claro, then Movistar, the state incumbent CNT, and regional telcos like Cuenca's municipal ETAPA — so a household's resolver is whatever its provider assigns. These networks meet at NAP.EC in Quito and Guayaquil, and a block at the exchange reaches much of the country at once.
Checking a record from inside Ecuador shows what those resolvers actually return, ARCOTEL-ordered blocks included, not the answer 8.8.8.8 gives from abroad. A domain that resolves elsewhere but comes back empty on a Claro or CNT line is filtered, not broken.
- Claro (CONECEL)190.63.6.5 Largest operator; default resolver for most subscribers
- CNT EP190.152.5.126 State-owned incumbent; anycast resolver on its andinanet network
- Movistar (Otecel) Telefónica's Ecuadorian network; default resolver for its lines
- ETAPA EP191.100.22.36 Cuenca's municipally-owned telco; regional default resolver
Some answers from Ecuadorian ISP resolvers can be shaped by ARCOTEL-ordered blocking, which providers and the NAP.EC exchange carry out at the DNS layer under a long-standing, unpublished agreement, so a blocked domain may resolve differently through a local operator than through a public resolver abroad.
How DNS propagation works
Every DNS record carries a time-to-live: the seconds a resolver may keep its cached answer before asking again. Change a record and resolvers holding the old value keep serving it until that timer runs out.
Propagation is this expiry playing out across many independent resolvers, so a lower time-to-live set ahead of a change makes it take effect sooner. There is no fixed waiting period — each record's time-to-live decides how long the old answer lingers.
Frequently Asked Questions
Why do DNS servers in Ecuador return different results than 8.8.8.8?
Two things cause it. Each resolver caches independently, so one can hold an older answer than another.
And content delivery networks reply based on where the asking resolver is, steering a resolver in Ecuador toward a nearby edge node.
Both answers can be correct at the same time for their own location.
How long until a DNS change is visible in Ecuador?
It depends on the record's time-to-live, not on the country.
Resolvers in Ecuador keep the previous answer until their cached copy expires, then pick up the new one.
If you lowered the time-to-live before making the change, it appears sooner; otherwise the old value can persist until the original timer elapses.
Which DNS server should users in Ecuador use?
For most people the resolver their internet provider assigns is fine and usually the lowest latency.
Anyone who wants an alternative can point to a public resolver reachable from Ecuador, such as Cloudflare (1.1.1.1) or Google (8.8.8.8); the right choice depends on whether you value speed, privacy, or filtering.
Why check DNS from Ecuador specifically?
Because it shows what visitors in Ecuador actually resolve, which can differ from a global lookup.
If your audience is in Ecuador, or you have moved hosting or mail there, checking against in-country resolvers confirms the records have reached the servers those users rely on.
Why does a site resolve on 8.8.8.8 but fail on my Claro or CNT connection in Ecuador?
Ecuadorian blocking is applied at the DNS layer. When ARCOTEL orders a domain blocked, providers and the NAP.EC exchange return a wrong or empty answer for it, while a public resolver like Google's 8.8.8.8 or Cloudflare's 1.1.1.1 sits outside that arrangement and usually hands back the real record. The EFF has pointed out that an internet exchange is the natural place to inject false DNS replies, which is roughly what happened in 2014 when Google and YouTube were briefly cut off nationwide. One caveat: where a block is enforced at the IP layer instead, a correct DNS answer still will not make the site load.
Who decides what gets blocked in Ecuador?
ARCOTEL, the telecom regulator, is authorized to order domains blocked under national law, and AEPROVI carries those orders out. AEPROVI's members carry more than 95% of the country's traffic and operate the NAP.EC exchange points in Quito and Guayaquil, and they have blocked domains under a cooperation agreement with the telecoms regulator signed in 2012. The text of that agreement has never been made public and the exact mechanism is undisclosed, so a DNS check from inside Ecuador is one of the few ways to see whether a domain has been swept into it.
