Network · data from 2026-11-12
AS54355 MULTCO - NETWORK SERVICES
Registry name: MULTCO - NETWORK SERVICES, US · not in PeeringDB
10IPv4 routes
0.0% RPKI valid · 20.0% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
10No ROA
8 with no route object for this origin
6Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS54355, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS54355, 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.
| 205.153.49.0/24 | No ROA | Nonecovered by 205.153.48.0/22 | 671 100% |
| 205.173.223.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 671 100% |
| 205.173.216.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 3 0%low visibility |
| 205.173.220.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 2 0%low visibility |
| 205.173.217.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 1 0%low visibility |
| 205.173.218.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 1 0%low visibility |
| 205.173.219.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 1 0%low visibility |
| 205.173.221.0/24 | No ROA | Nonecovered by 205.173.216.0/21 | 1 0%low visibility |
| 205.173.216.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 205.153.48.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS54355 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 20 are in fix.csv.
- ROA: none10
- Route object: none8
- Route object: RIR2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 205.153.49.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.153.49.0/24 | No route object for it. A route object for 205.153.48.0/22 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.223.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.223.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.216.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.216.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.220.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.220.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.217.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.217.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.218.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.218.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.219.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.219.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.221.0/24 | No ROA covers it. Add a ROA for AS54355, maxLength 24. |
| Route object: none | 205.173.221.0/24 | No route object for it. A route object for 205.173.216.0/21 with origin AS54355 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54355 in the RIR database for the space. |
| ROA: none | 205.173.216.0/21 | No ROA covers it. Add a ROA for AS54355, maxLength 21. |
| Route object: RIR | 205.173.216.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.153.48.0/22 | No ROA covers it. Add a ROA for AS54355, maxLength 22. |
| Route object: RIR | 205.153.48.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS54355 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.