bgpreport

Network · data from 2026-11-12

AS21873 NEWMN

Registry name: NEWMN - Northeast Service Cooperative (ASN-NEWMN), US · PeeringDB

26IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS21873, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21873, 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.199.192.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.193.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.194.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.195.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.196.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.197.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.198.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.199.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.200.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.201.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.202.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.204.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.205.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.206.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.207.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.211.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.214.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.215.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.216.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.217.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.218.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.221.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.222.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.223.0/24 Valid Other IRR onlyRADB 671 100% 68
66.199.210.0/24 Valid RIR databaseARIN 673 100% 67
66.199.192.0/19 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

AS21873'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 28 are in fix.csv.

  • Route object: RIR24
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR66.199.192.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.193.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.194.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.195.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.196.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.197.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.198.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.199.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.200.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.201.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.202.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.204.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.205.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.206.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.207.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.211.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.214.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.215.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.216.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.217.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.218.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.221.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.222.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR66.199.223.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS21873 whose prefix no peer sees AS21873 announce. Many are kept on purpose (backup routes, space announced only in some places).

66.199.203.0/24RADBValid
66.199.208.0/24RADBValid
66.199.212.0/24RADBValid
2604:8680::/32ARINValid

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.