bgpreport

Network · data from 2026-11-12

AS268244 AS268244 - SPEEDNET CR

Registry name: AS268244 - SPEEDNET CR, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268244, 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.
45.236.180.0/23 No ROA Nonecovered by 45.236.180.0/22 671 100% 67
45.236.182.0/23 No ROA Nonecovered by 45.236.180.0/22 671 100% 67
2804:4e2c:aa::/48 No ROA Nonecovered by 2804:4e2c::/32 633 100% 67
45.236.180.0/22 No ROA Other IRR onlyRADB 672 100% 67
38.10.138.0/24 No ROA Other IRR onlyRADB 671 100% 67
2804:4e2c::/32 No ROA Other IRR onlyRADB 633 100% 67

AS-SET

AS268244 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: none45.236.180.0/23No ROA covers it. Add a ROA for AS268244, maxLength 23.671 of 673
Route object: none45.236.180.0/23No route object for it. A route object for 45.236.180.0/22 with origin AS268244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268244 in the RIR database for the space.671 of 673
ROA: none45.236.182.0/23No ROA covers it. Add a ROA for AS268244, maxLength 23.671 of 673
Route object: none45.236.182.0/23No route object for it. A route object for 45.236.180.0/22 with origin AS268244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268244 in the RIR database for the space.671 of 673
ROA: none2804:4e2c:aa::/48No ROA covers it. Add a ROA for AS268244, maxLength 48.633 of 636
Route object: none2804:4e2c:aa::/48No route object for it. A route object for 2804:4e2c::/32 with origin AS268244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268244 in the RIR database for the space.633 of 636
ROA: none45.236.180.0/22No ROA covers it. Add a ROA for AS268244, maxLength 22.672 of 673
Route object: RIR45.236.180.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.10.138.0/24No ROA covers it. Add a ROA for AS268244, maxLength 24.671 of 673
Route object: RIR38.10.138.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:4e2c::/32No ROA covers it. Add a ROA for AS268244, maxLength 32.633 of 636
Route object: RIR2804:4e2c::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

Every route object with origin AS268244 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.