bgpreport

Network · data from 2026-11-12

AS25808 CONCORD-MA - Town of Concord MA

Registry name: CONCORD-MA - Town of Concord MA, US · not in PeeringDB

15IPv4 routes 13.3% RPKI valid · 40.0% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
11No ROA 9 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS25808, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS25808, 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.

65.51.103.0/24 Invalid: origin None 49 7%low visibility 30
69.74.58.0/24 Invalid: origin None 49 7%low visibility 30
38.242.8.0/24 No ROA Other origin onlycovered by 38.242.8.0/22 671 100% 67
38.242.9.0/24 No ROA Other origin onlycovered by 38.242.8.0/22 671 100% 67
38.242.10.0/24 No ROA Other origin onlycovered by 38.242.8.0/22 671 100% 67
38.242.11.0/24 No ROA Other origin onlycovered by 38.242.8.0/22 671 100% 67
172.110.60.0/24 No ROA Other origin onlycovered by 172.110.60.0/22 671 100% 68
172.110.61.0/24 No ROA Other origin onlycovered by 172.110.60.0/22 671 100% 68
172.110.62.0/24 No ROA Other origin onlycovered by 172.110.60.0/22 671 100% 68
38.97.130.0/24 No ROA Other IRR onlyRADB 671 100% 68
38.97.136.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.125.66.0/24 No ROA Other IRR onlyRADB 671 100% 68
199.125.68.0/24 No ROA Other IRR onlyRADB 671 100% 68
47.19.118.0/24 Valid RIR databaseARIN 671 100% 68
148.76.116.0/24 Valid RIR databaseARIN 671 100% 68

AS-SET

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

  • ROA: origin2
  • ROA: none11
  • Route object: none9
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin65.51.103.0/24ROAs covering it name AS6128, AS54004, not AS25808. If AS25808 should announce it, add a ROA for AS25808.49 of 673
Route object: none65.51.103.0/24No route object for it. Add a route object with origin AS25808 in the RIR database for the space.49 of 673
ROA: origin69.74.58.0/24ROAs covering it name AS6128, AS54004, not AS25808. If AS25808 should announce it, add a ROA for AS25808.49 of 673
Route object: none69.74.58.0/24No route object for it. Add a route object with origin AS25808 in the RIR database for the space.49 of 673
ROA: none38.242.8.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none38.242.8.0/24Route objects for it name AS46887. A route object for 38.242.8.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none38.242.9.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none38.242.9.0/24Route objects for it name AS46887. A route object for 38.242.8.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none38.242.10.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none38.242.10.0/24Route objects for it name AS46887. A route object for 38.242.8.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none38.242.11.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none38.242.11.0/24Route objects for it name AS46887. A route object for 38.242.8.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none172.110.60.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none172.110.60.0/24Route objects for it name AS33748, AS46887. A route object for 172.110.60.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none172.110.61.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none172.110.61.0/24Route objects for it name AS33748, AS46887. A route object for 172.110.60.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none172.110.62.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: none172.110.62.0/24Route objects for it name AS33748, AS46887. A route object for 172.110.60.0/22 with origin AS25808 covers it (filters allowing more-specifics accept it). Add a route object with origin AS25808 in the RIR database for the space.671 of 673
ROA: none38.97.130.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: RIR38.97.130.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.97.136.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: RIR38.97.136.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.125.66.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: RIR199.125.66.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none199.125.68.0/24No ROA covers it. Add a ROA for AS25808, maxLength 24.671 of 673
Route object: RIR199.125.68.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 AS25808 whose prefix no peer sees AS25808 announce. Many are kept on purpose (backup routes, space announced only in some places).

38.242.8.0/22RADBNo ROA
172.110.60.0/22RADBNo ROA

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.