Network · data from 2026-11-12
AS402671 FROCEL - Frontier
Registry name: FROCEL - Frontier, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402671, 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.
| 189.30.118.0/24 | Invalid: origin | Other origin only | 3 0%low visibility |
| 160.21.148.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 94.118.137.0/24 | Invalid: origin | Other IRR onlyRADB | 3 0%low visibility |
| 13.141.72.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 94.118.204.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 189.31.5.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 189.31.25.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 200.138.35.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 200.141.63.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 189.30.82.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 191.45.38.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 179.69.104.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
| 2a04:7a80::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a05:c580::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a0b:2e40::/29 | Valid | RIR databaseRIPE | 635 100% |
| 2a0a:5700::/29 | Valid | RIR databaseRIPE | 634 100% |
| 2a10:ee80::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a10:f280::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a11:e1c0::/29 | Valid | RIR databaseRIPE | 633 100% |
| 2a09:1c0::/29 | Valid | RIR databaseRIPE | 632 99% |
| 179.254.205.0/24 | Valid | RIR databaseRADB, RIPE | 3 0%low visibility |
| 189.30.120.0/24 | Valid | RIR databaseRADB, RIPE | 3 0%low visibility |
| 176.102.174.0/24 | Valid | RIR databaseRADB, RIPE | 1 0%low visibility |
AS-SET
AS402671 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 23 are in fix.csv.
- ROA: origin3
- Route object: none2
- Route object: RIR1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 189.30.118.0/24 | ROAs covering it name AS834, not AS402671. If AS402671 should announce it, add a ROA for AS402671. |
| Route object: none | 189.30.118.0/24 | Route objects for it name AS834. Add a route object with origin AS402671 in the RIR database for the space. |
| ROA: origin | 160.21.148.0/24 | ROAs covering it name AS834, not AS402671. If AS402671 should announce it, add a ROA for AS402671. |
| Route object: none | 160.21.148.0/24 | Route objects for it name AS834. Add a route object with origin AS402671 in the RIR database for the space. |
| ROA: origin | 94.118.137.0/24 | ROAs covering it name AS834, not AS402671. If AS402671 should announce it, add a ROA for AS402671. |
| Route object: RIR | 94.118.137.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS402671 whose prefix no peer sees AS402671 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 13.141.8.0/24 | RADB, RIPE | Valid |
| 23.88.248.0/24 | ARIN, RADB | Valid |
| 65.86.203.0/24 | ARIN, RADB | Valid |
| 87.84.16.0/24 | RADB, RIPE | Valid |
| 90.96.112.0/24 | RADB, RIPE | Valid |
| 90.96.124.0/24 | RADB, RIPE | Valid |
| 94.118.147.0/24 | RADB, RIPE | Valid |
| 152.234.159.0/24 | RADB, RIPE | Valid |
| 160.21.149.0/24 | RADB, RIPE | Valid |
| 168.199.153.0/24 | RADB, RIPE | Valid |
| 177.201.195.0/24 | RADB, RIPE | Valid |
| 178.93.221.0/24 | RADB, RIPE | Valid |
| 179.253.45.0/24 | RADB, RIPE | Valid |
| 187.55.33.0/24 | RADB, RIPE | Valid |
| 189.73.44.0/24 | RADB, RIPE | Valid |
| 191.0.81.0/24 | RADB, RIPE | Valid |
| 200.149.190.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.