bgpreport

Network · data from 2026-11-12

AS26403 MADERACOE - Madera County Office of Education

Registry name: MADERACOE - Madera County Office of Education, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26403, 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.
206.78.127.248/29 No ROA Nonecovered by 206.78.120.0/21 1 0%low visibility 1
206.78.127.248/30 No ROA Nonecovered by 206.78.120.0/21 1 0%low visibility 1
206.78.127.252/30 No ROA Nonecovered by 206.78.120.0/21 1 0%low visibility 1
206.78.114.0/23 No ROA Other IRR onlyRADB 669 99% 68
206.78.116.0/22 No ROA Other IRR onlyRADB 669 99% 68
206.78.120.0/21 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS26403 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: none206.78.127.248/29No ROA covers it. Add a ROA for AS26403, maxLength 29.1 of 673
Route object: none206.78.127.248/29No route object for it. A route object for 206.78.120.0/21 with origin AS26403 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS26403 in the RIR database for the space.1 of 673
ROA: none206.78.127.248/30No ROA covers it. Add a ROA for AS26403, maxLength 30.1 of 673
Route object: none206.78.127.248/30No route object for it. A route object for 206.78.120.0/21 with origin AS26403 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS26403 in the RIR database for the space.1 of 673
ROA: none206.78.127.252/30No ROA covers it. Add a ROA for AS26403, maxLength 30.1 of 673
Route object: none206.78.127.252/30No route object for it. A route object for 206.78.120.0/21 with origin AS26403 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS26403 in the RIR database for the space.1 of 673
ROA: none206.78.114.0/23No ROA covers it. Add a ROA for AS26403, maxLength 23.669 of 673
Route object: RIR206.78.114.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none206.78.116.0/22No ROA covers it. Add a ROA for AS26403, maxLength 22.669 of 673
Route object: RIR206.78.116.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none206.78.120.0/21No ROA covers it. Add a ROA for AS26403, maxLength 21.669 of 673
Route object: RIR206.78.120.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS26403 is announced.

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.