bgpreport

Network · data from 2026-11-12

AS269097 CYBERNET LTDA

Registry name: AS269097 - CYBERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269097, 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.
2804:5f68:8000::/33 No ROA Nonecovered by 2804:5f68::/32 632 99% 67
45.179.159.0/24 No ROA Other IRR onlyRADB 668 99% 66
45.179.156.0/24 No ROA Other IRR onlyRADB 667 99% 67
45.179.158.0/24 No ROA Other IRR onlyRADB 667 99% 66
45.179.157.0/24 No ROA Other IRR onlyRADB 666 99% 67
45.179.156.0/22 No ROA Other IRR onlyALTDB, RADB 665 99% 66
2804:5f68::/32 No ROA Other IRR onlyALTDB, RADB 632 99% 67

AS-SET

AS269097'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 17 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:5f68:8000::/33No ROA covers it. Add a ROA for AS269097, maxLength 33.632 of 636
Route object: none2804:5f68:8000::/33No route object for it. A route object for 2804:5f68::/32 with origin AS269097 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269097 in the RIR database for the space.632 of 636
ROA: none45.179.159.0/24No ROA covers it. Add a ROA for AS269097, maxLength 24.668 of 673
Route object: RIR45.179.159.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.179.156.0/24No ROA covers it. Add a ROA for AS269097, maxLength 24.667 of 673
Route object: RIR45.179.156.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.179.158.0/24No ROA covers it. Add a ROA for AS269097, maxLength 24.667 of 673
Route object: RIR45.179.158.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.179.157.0/24No ROA covers it. Add a ROA for AS269097, maxLength 24.666 of 673
Route object: RIR45.179.157.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none45.179.156.0/22No ROA covers it. Add a ROA for AS269097, maxLength 22.665 of 673
Route object: RIR45.179.156.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:5f68::/32No ROA covers it. Add a ROA for AS269097, maxLength 32.632 of 636
Route object: RIR2804:5f68::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

45.4.176.0/22RADBNo ROA
45.179.156.0/23RADBNo ROA
45.179.158.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.