Network · data from 2026-11-12
AS402535 MOORGADE - Moorgade
Registry name: MOORGADE - Moorgade, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402535, 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.
| 64.204.166.0/24 | Invalid: origin | None | 2 0%low visibility |
AS-SET
AS402535 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: origin1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 64.204.166.0/24 | ROAs covering it name AS834, not AS402535. If AS402535 should announce it, add a ROA for AS402535. |
| Route object: none | 64.204.166.0/24 | No route object for it. Add a route object with origin AS402535 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402535 whose prefix no peer sees AS402535 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.167.164.0/24 | ARIN | Valid |
| 51.241.7.0/24 | RADB, RIPE | Valid |
| 86.38.235.0/24 | RADB, RIPE | Valid |
| 178.95.170.0/24 | RADB, RIPE | Valid |
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.