bgpreport

Network · data from 2026-11-12

AS26696 MINTO-COMMUNICATIONS-SOCIETY - Minto Communications Society

Registry name: MINTO-COMMUNICATIONS-SOCIETY - Minto Communications Society, CA · not in PeeringDB

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

Announced routes

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

64.114.125.0/24 Invalid: origin None 41 6%low visibility 24
209.52.32.0/24 Invalid: origin None 41 6%low visibility 24
64.6.40.0/24 No ROA Other IRR onlyRADB 671 100% 67
64.6.41.0/24 No ROA Other IRR onlyRADB 671 100% 67

AS-SET

AS26696 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 9 are in fix.csv.

  • ROA: origin2
  • ROA: none2
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin64.114.125.0/24ROAs covering it name AS852, not AS26696. If AS26696 should announce it, add a ROA for AS26696.41 of 673
Route object: none64.114.125.0/24No route object for it. Add a route object with origin AS26696 in the RIR database for the space.41 of 673
ROA: origin209.52.32.0/24ROAs covering it name AS852, not AS26696. If AS26696 should announce it, add a ROA for AS26696.41 of 673
Route object: none209.52.32.0/24No route object for it. Add a route object with origin AS26696 in the RIR database for the space.41 of 673
ROA: none64.6.40.0/24No ROA covers it. Add a ROA for AS26696, maxLength 24.671 of 673
Route object: RIR64.6.40.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none64.6.41.0/24No ROA covers it. Add a ROA for AS26696, maxLength 24.671 of 673
Route object: RIR64.6.41.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 AS26696 whose prefix no peer sees AS26696 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.6.40.0/23RADBNo 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.