Network · data from 2026-11-12
AS54549 VIP-FIBER - City of Vallejo, A municipal corporation
Registry name: VIP-FIBER - City of Vallejo, A municipal corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54549, 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.
| 66.223.104.0/23 | Valid | Nonecovered by 66.223.104.0/22 | 673 100% |
| 66.223.106.0/24 | Valid | Nonecovered by 66.223.104.0/22 | 673 100% |
| 208.184.160.0/24 | Valid | Other IRR onlyALTDB | 673 100% |
| 2606:ff40::/32 | Valid | RIR databaseARIN | 634 100% |
AS-SET
AS54549 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 4 are in fix.csv.
- Route object: none2
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 66.223.104.0/23 | No route object for it. A route object for 66.223.104.0/22 with origin AS54549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54549 in the RIR database for the space. |
| Route object: none | 66.223.106.0/24 | No route object for it. A route object for 66.223.104.0/22 with origin AS54549 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54549 in the RIR database for the space. |
| Route object: RIR | 208.184.160.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54549 whose prefix no peer sees AS54549 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 66.223.104.0/22 | ARIN | 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.