Network · data from 2026-11-12
AS401763 BLUEPULSENETWORKSLLC - Blue Pulse Networks LLC
Registry name: BLUEPULSENETWORKSLLC - Blue Pulse Networks LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS401763, 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.
| 12.18.148.0/24 | No ROA | None | 673 100% |
| 23.168.224.0/24 | No ROA | None | 673 100% |
| 2602:fe23::/36 | No ROA | None | 635 100% |
AS-SET
AS401763 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 6 are in fix.csv.
- ROA: none3
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 12.18.148.0/24 | No ROA covers it. Add a ROA for AS401763, maxLength 24. |
| Route object: none | 12.18.148.0/24 | No route object for it. Add a route object with origin AS401763 in the RIR database for the space. |
| ROA: none | 23.168.224.0/24 | No ROA covers it. Add a ROA for AS401763, maxLength 24. |
| Route object: none | 23.168.224.0/24 | No route object for it. Add a route object with origin AS401763 in the RIR database for the space. |
| ROA: none | 2602:fe23::/36 | No ROA covers it. Add a ROA for AS401763, maxLength 36. |
| Route object: none | 2602:fe23::/36 | No route object for it. Add a route object with origin AS401763 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS401763 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.