Network · data from 2026-11-12
AS400755 GO-DADDY-COM-LLC - GoDaddy.com, LLC
Registry name: GO-DADDY-COM-LLC - GoDaddy.com, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400755, 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.
| 132.148.54.0/24 | Invalid: origin | Other origin only | 37 5%low visibility |
AS-SET
AS400755 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 2 are in fix.csv.
- ROA: origin1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 132.148.54.0/24 | ROAs covering it name AS26496, AS398101, not AS400755. If AS400755 should announce it, add a ROA for AS400755. |
| Route object: none | 132.148.54.0/24 | Route objects for it name AS398101. Add a route object with origin AS400755 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS400755 is announced.
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.