Network · data from 2026-11-12
AS22018 Taunton Municipal Lighting Plant
Registry name: TAUNTON-MUNICIPAL - Taunton Municipal Lighting Plant, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS22018, 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.
| 69.64.96.0/21 | Valid | Nonecovered by 69.64.96.0/20 | 670 100% |
| 69.64.104.0/21 | Valid | Nonecovered by 69.64.96.0/20 | 670 100% |
| 209.25.208.0/24 | Valid | Nonecovered by 209.25.208.0/22 | 670 100% |
| 209.25.209.0/24 | Valid | Nonecovered by 209.25.208.0/22 | 670 100% |
| 209.25.210.0/24 | Valid | Nonecovered by 209.25.208.0/22 | 670 100% |
| 209.25.211.0/24 | Valid | Nonecovered by 209.25.208.0/22 | 670 100% |
| 69.64.96.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
AS-SET
AS22018's PeeringDB record names no 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 9 are in fix.csv.
- Route object: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 69.64.96.0/21 | No route object for it. A route object for 69.64.96.0/20 with origin AS22018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22018 in the RIR database for the space. |
| Route object: none | 69.64.104.0/21 | No route object for it. A route object for 69.64.96.0/20 with origin AS22018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22018 in the RIR database for the space. |
| Route object: none | 209.25.208.0/24 | No route object for it. A route object for 209.25.208.0/22 with origin AS22018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22018 in the RIR database for the space. |
| Route object: none | 209.25.209.0/24 | No route object for it. A route object for 209.25.208.0/22 with origin AS22018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22018 in the RIR database for the space. |
| Route object: none | 209.25.210.0/24 | No route object for it. A route object for 209.25.208.0/22 with origin AS22018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22018 in the RIR database for the space. |
| Route object: none | 209.25.211.0/24 | No route object for it. A route object for 209.25.208.0/22 with origin AS22018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22018 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS22018 whose prefix no peer sees AS22018 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.25.208.0/22 | ARIN, RADB | Valid |
| 2001:470:421::/48 | ARIN | Valid |
| 2001:470:5b3::/48 | 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.