bgpreport

Network · data from 2026-11-12

AS400754 GO-DADDY-COM-LLC - GoDaddy.com, LLC

Registry name: GO-DADDY-COM-LLC - GoDaddy.com, LLC, US · not in PeeringDB

13IPv4 routes 92.3% RPKI valid · 46.2% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 7 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS400754, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400754, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
173.201.200.0/23 No ROA None 671 100% 67
50.63.4.0/23 Valid None 671 100% 67
97.74.72.0/22 Valid None 671 100% 67
198.71.248.0/22 Valid None 671 100% 67
208.109.132.0/23 Valid None 671 100% 67
97.74.76.0/24 Valid None 670 100% 67
132.148.185.0/24 Valid Nonecovered by 132.148.184.0/21 670 100% 67
198.71.224.0/21 Valid RIR databaseARIN 673 100% 67
148.72.16.0/22 Valid RIR databaseARIN 671 100% 67
50.62.152.0/24 Valid RIR databaseARIN 670 100% 67
198.71.254.0/24 Valid RIR databaseARIN 670 100% 67
107.180.0.0/18 Valid RIR databaseARIN 2 0%low visibility 2
148.72.4.0/22 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS400754 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.

  • ROA: none1
  • Route object: none7
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none173.201.200.0/23No ROA covers it. Add a ROA for AS400754, maxLength 23.671 of 673
Route object: none173.201.200.0/23No route object for it. Add a route object with origin AS400754 in the RIR database for the space.671 of 673
Route object: none50.63.4.0/23No route object for it. Add a route object with origin AS400754 in the RIR database for the space.671 of 673
Route object: none97.74.72.0/22No route object for it. Add a route object with origin AS400754 in the RIR database for the space.671 of 673
Route object: none198.71.248.0/22No route object for it. Add a route object with origin AS400754 in the RIR database for the space.671 of 673
Route object: none208.109.132.0/23No route object for it. Add a route object with origin AS400754 in the RIR database for the space.671 of 673
Route object: none97.74.76.0/24No route object for it. Add a route object with origin AS400754 in the RIR database for the space.670 of 673
Route object: none132.148.185.0/24No route object for it. A route object for 132.148.184.0/21 with origin AS400754 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400754 in the RIR database for the space.670 of 673

Route objects not announced

Route objects with origin AS400754 whose prefix no peer sees AS400754 announce. Many are kept on purpose (backup routes, space announced only in some places).

50.62.153.0/24ARINValid
107.180.108.0/22ARINValid
107.180.120.0/22ARINValid
132.148.184.0/21ARINValid
198.71.232.0/21ARINValid
198.71.240.0/22ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.