dns.pizza standing page

If Amazon Route 53's DNS fails, what goes dark?

Data snapshot of November 1, 2026. Nameservers last checked September 5, 2026 to November 1, 2026. This page is a map of who depends on Amazon Route 53. It is not a live reading and does not say whether Amazon Route 53 has a problem right now.

18,259 of the 99,283 top-ranked domains (18.4%) use Amazon Route 53 as their only DNS operator. If its nameservers stopped answering, these are the sites whose name could no longer be looked up once cached answers expired. Another 211 use Amazon Route 53 together with a another listed operator and may keep resolving, if that operator is independent and working.

DNS is the lookup that turns a name into an address. When none of a domain's nameservers answer, new lookups fail as cached answers run out, which takes from minutes to a day or more depending on each site's settings. People who already have the address, or reach it directly, may still get through.

18,259

depend on Amazon Route 53 alone, 18.4% of 99,283

219 of 996

of the top 1,000 sites depend on it alone

211

use it plus another listed operator, so they may stay up

Highest-ranked sites that depend on Amazon Route 53 alone

Top 100 of 18,259 by Tranco rank (1 is the most popular). The full list is in the CSV and JSON.

  1. amazonaws.com#9
  2. amazon.com#25
  3. appsflyersdk.com#34
  4. netflix.com#40
  5. cloudfront.net#51
  6. vimeo.com#71
  7. zoom.us#77
  8. pv-cdn.net#78
  9. reddit.com#101
  10. ui.com#104
  11. a2z.com#108
  12. amazon-adsystem.com#119
  13. epicgames.com#121
  14. snapchat.com#124
  15. apache.org#125
  16. amazonvideo.com#128
  17. amazon.dev#130
  18. prodregistryv2.org#136
  19. dropbox.com#139
  20. adobe.io#168
  21. flickr.com#173
  22. soundcloud.com#177
  23. aws.dev#181
  24. cnn.com#190
  25. forbes.com#201
  26. twitch.tv#214
  27. canva.com#231
  28. stripe.com#241
  29. scorecardresearch.com#242
  30. roku.com#245
  31. meraki.com#251
  32. linktr.ee#255
  33. booking.com#256
  34. forter.com#257
  35. ttvnw.net#273
  36. lsrelayaccess.com#275
  37. samsungcloud.com#283
  38. heytapmobile.com#291
  39. shalltry.com#298
  40. appsflyer.com#301
  41. media-amazon.com#302
  42. samsungqbe.com#305
  43. mtgglobals.com#307
  44. autodesk.com#308
  45. amazon.co.uk#313
  46. amplitude.com#314
  47. launchdarkly.com#320
  48. issuu.com#330
  49. slack.com#332
  50. weebly.com#336
  51. aol.com#342
  52. onelink.me#346
  53. quickconnect.to#349
  54. allawnos.com#350
  55. wbx2.com#352
  56. wsj.com#353
  57. trustpilot.com#355
  58. ezvizlife.com#356
  59. 3lift.com#357
  60. tradingview.com#361
  61. samsungcloudsolution.com#369
  62. browser-intake-datadoghq.com#375
  63. live-video.net#384
  64. tp-link.com#385
  65. amazon.de#391
  66. heytapdl.com#393
  67. zendesk.com#396
  68. amagi.tv#405
  69. awswaf.com#420
  70. supercell.com#422
  71. espn.com#423
  72. avsxappcaptiveportal.com#431
  73. sc-gw.com#437
  74. statista.com#440
  75. awsglobalaccelerator.com#442
  76. amazontrust.com#443
  77. bsky.app#444
  78. eventbrite.com#450
  79. featureassets.org#453
  80. speedtest.net#454
  81. quora.com#455
  82. nflximg.com#457
  83. duolingo.com#462
  84. firetvcaptiveportal.com#463
  85. goodreads.com#465
  86. scribd.com#467
  87. npr.org#468
  88. arubanetworks.com#475
  89. shein.com#489
  90. beyondwickedmapping.org#491
  91. amazon.co.jp#492
  92. behance.net#497
  93. slideshare.net#499
  94. nflxvideo.net#505
  95. docker.com#510
  96. wired.com#511
  97. ft.com#514
  98. elasticbeanstalk.com#516
  99. fandom.com#524
  100. vidaahub.com#529
How many depend on Amazon Route 53 alone, by rank
Rank bandAloneOf domains in band
1 to 1,00021922.0% of 996
1,001 to 10,0002,20323.8% of 9,248
10,001 to 100,00015,83717.8% of 89,039

Sites that use Amazon Route 53 and also list another operator

Top 100 of 211, with the other operator. These may keep resolving if Amazon Route 53 alone fails, provided the other operator is genuinely independent and working. We do not test that.

  1. github.com#29also on NS1 (IBM)
  2. bit.ly#103also on Google
  3. github.io#122also on NS1 (IBM)
  4. nytimes.com#155also on NS1 (IBM)
  5. etsy.com#296also on NS1 (IBM)
  6. washingtonpost.com#359also on UltraDNS (Vercara)
  7. okta.com#548also on Google
  8. service.gov.uk#654also on Google
  9. githubusercontent.com#732also on NS1 (IBM)
  10. mlb.com#764also on Google
  11. pornhub.com#843also on UltraDNS (Vercara)
  12. airbnb.com#918also on NS1 (IBM)
  13. theatlantic.com#948also on Google
  14. phncdn.com#1,160also on UltraDNS (Vercara)
  15. youporn.com#1,259also on UltraDNS (Vercara)
  16. redtube.com#1,304also on UltraDNS (Vercara)
  17. pornhub.org#1,371also on UltraDNS (Vercara)
  18. thousandeyes.com#2,518also on Google
  19. trafficjunky.net#2,816also on UltraDNS (Vercara)
  20. irishtimes.com#2,867also on Google
  21. ning.com#3,201also on its own nameservers
  22. bitly.com#3,419also on Google
  23. sbb.ch#3,661also on its own nameservers
  24. twtrdns.net#3,931also on UltraDNS (Vercara)
  25. srf.ch#4,380also on NS1 (IBM)
  26. etrade.com#4,492also on UltraDNS (Vercara)
  27. justwatch.com#4,534also on Google
  28. adtng.com#4,676also on UltraDNS (Vercara)
  29. githubassets.com#4,774also on NS1 (IBM)
  30. etsystatic.com#4,936also on NS1 (IBM)
  31. inquirer.com#5,596also on NS1 (IBM)
  32. oktacdn.com#5,696also on Google
  33. esri.com#5,738also on Akamai
  34. nyt.com#5,790also on NS1 (IBM)
  35. playtika.com#5,804also on NS1 (IBM)
  36. delfi.lt#5,862also on its own nameservers, domreg.lt
  37. homeoffice.gov.uk#5,871also on Microsoft Azure DNS
  38. telecinco.es#6,295also on Akamai
  39. pingone.com#6,316also on DNS Made Easy
  40. bp.com#6,811also on Cloudflare
  41. tube8.com#7,213also on UltraDNS (Vercara)
  42. rrbapply.gov.in#7,411also on diginame.in
  43. thumbzilla.com#7,531also on UltraDNS (Vercara)
  44. freshporno.net#8,476also on UltraDNS (Vercara)
  45. tube8.fr#8,927also on UltraDNS (Vercara)
  46. redtube.com.br#9,232also on UltraDNS (Vercara)
  47. pornhits.com#9,572also on UltraDNS (Vercara)
  48. milb.com#10,332also on Google
  49. trafficjunky.com#10,613also on UltraDNS (Vercara)
  50. muscache.com#10,796also on NS1 (IBM)
  51. airbnb.co.uk#10,919also on NS1 (IBM)
  52. okta-emea.com#11,101also on Google
  53. radwarecloud.net#11,377also on Google
  54. etahub.com#11,460also on UltraDNS (Vercara)
  55. editmysite.com#11,689also on NS1 (IBM)
  56. airbnb.fr#11,714also on NS1 (IBM)
  57. nutaku.net#12,284also on UltraDNS (Vercara)
  58. sncf-connect.com#12,320also on Cloudflare
  59. data.gov.uk#12,771also on Google
  60. ypncdn.com#13,838also on UltraDNS (Vercara)
  61. oktapreview.com#14,536also on Google
  62. rts.ch#15,476also on NS1 (IBM)
  63. nyt.net#15,580also on NS1 (IBM)
  64. mydirtyhobby.de#15,691also on UltraDNS (Vercara)
  65. epoq.de#15,739also on DNS Made Easy
  66. mlbinfra.com#15,752also on Google
  67. airbnb.com.br#16,408also on NS1 (IBM)
  68. nitori-net.jp#16,601also on vips.ne.jp
  69. simplevoip.us#17,299also on easyDNS
  70. j.mp#17,534also on Google
  71. commander1.com#18,256also on cdnetdns.net
  72. pornhubpremium.com#18,357also on UltraDNS (Vercara)
  73. mlbstatic.com#18,410also on Google
  74. iht.com#18,805also on NS1 (IBM)
  75. antena3.com#18,987also on Cloudflare
  76. tagcommander.com#19,511also on cdnetdns.net
  77. yext.com#20,296also on Google
  78. githubapp.com#20,696also on NS1 (IBM)
  79. airbnb.ca#20,815also on NS1 (IBM)
  80. pingone.eu#21,296also on DNS Made Easy
  81. you-porn.com#21,335also on UltraDNS (Vercara)
  82. redtubepremium.com#21,403also on UltraDNS (Vercara)
  83. 6pm.com#21,745also on Akamai
  84. lasexta.com#21,865also on Cloudflare
  85. kojka.com#22,674also on UltraDNS (Vercara)
  86. pornheal.com#22,703also on UltraDNS (Vercara)
  87. contentabc.com#22,753also on UltraDNS (Vercara)
  88. trustcommander.net#24,583also on cdnetdns.net
  89. atsptp.com#24,621also on UltraDNS (Vercara)
  90. nyti.ms#24,659also on NS1 (IBM)
  91. youpornpremium.com#24,664also on UltraDNS (Vercara)
  92. pingidentity.com#25,568also on DNS Made Easy
  93. adform.com#25,742also on Microsoft Azure DNS
  94. project1content.com#25,960also on UltraDNS (Vercara)
  95. rdtcdn.com#26,328also on UltraDNS (Vercara)
  96. tickets.com#26,563also on Google
  97. nelogica.com.br#26,574also on Microsoft Azure DNS
  98. airbnb.de#27,299also on NS1 (IBM)
  99. mktgcdn.com#27,350also on Google
  100. thewirecutter.com#27,572also on NS1 (IBM)

About this operator's numbers

Route 53 spreads each customer over four nameserver zones (awsdns-NN.com, .net, .org, .co.uk). Those four are one company, and are counted as one operator here.

What these figures do not capture

  • Hosting is a separate dependency. We record which nameservers a domain delegates to. We do not record CNAME targets, so we cannot tell a site that depends on a hosting platform (a store or site builder reached through a CNAME) from one that runs its own servers. A site on this list can fail for reasons that have nothing to do with Amazon Route 53, and a site not on it can fail because its host or CDN did.
  • Only the top 100,000 sites, one vote each. Tranco ranks popularity, not traffic. Smaller sites are not in this count, and a busy domain counts the same as a quiet one.
  • "Second operator" is not proof of independence. We treat each unrecognised nameserver zone as its own operator, so two zones owned by one company look like two. The count of sites that depend on Amazon Route 53 alone is therefore a floor, and the count with a second operator is a ceiling.
  • Vanity nameservers. A site that runs Amazon Route 53 under nameserver names on its own domain (ns1.example.com) is counted as self-hosted, not as a Amazon Route 53 customer.
  • Not every failure is total. An operator can fail in one region, one product, or for changes only (existing records keep answering). This page describes the worst case, every nameserver at one operator unreachable.
  • Snapshot timing. Domains move between operators. Records were last checked September 5, 2026 to November 1, 2026; a domain that changed operator after its check shows its old one.

Check right now

dns.pizza does not monitor Amazon Route 53 on this page and cannot say whether an outage is happening. To find out:

Use this data

Free to cite and reuse under CC BY 4.0; credit "dns.pizza" and the snapshot date (November 1, 2026). Method and the wider findings are in the research report One Outage From Darkness. Operator names are resolved from nameserver hostnames by the same rules as that report.