bgpreport

Network · data from 2026-11-12

AS269357 Inter fibra telecomunicação

Registry name: AS269357 - DELTA TELECOM, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269357, 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.185.44.0/23 No ROA Nonecovered by 45.185.44.0/22 670 100% 67
45.185.45.0/24 No ROA Nonecovered by 45.185.44.0/22 670 100% 67
45.185.44.0/24 No ROA Nonecovered by 45.185.44.0/22 669 99% 67
45.185.46.0/24 No ROA Nonecovered by 45.185.44.0/22 669 99% 67
45.185.47.0/24 No ROA Nonecovered by 45.185.44.0/22 2 0%low visibility 2

AS-SET

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

  • ROA: none5
  • Route object: none5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none45.185.44.0/23No ROA covers it. Add a ROA for AS269357, maxLength 23.670 of 673
Route object: none45.185.44.0/23No route object for it. A route object for 45.185.44.0/22 with origin AS269357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269357 in the RIR database for the space.670 of 673
ROA: none45.185.45.0/24No ROA covers it. Add a ROA for AS269357, maxLength 24.670 of 673
Route object: none45.185.45.0/24No route object for it. A route object for 45.185.44.0/22 with origin AS269357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269357 in the RIR database for the space.670 of 673
ROA: none45.185.44.0/24No ROA covers it. Add a ROA for AS269357, maxLength 24.669 of 673
Route object: none45.185.44.0/24No route object for it. A route object for 45.185.44.0/22 with origin AS269357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269357 in the RIR database for the space.669 of 673
ROA: none45.185.46.0/24No ROA covers it. Add a ROA for AS269357, maxLength 24.669 of 673
Route object: none45.185.46.0/24No route object for it. A route object for 45.185.44.0/22 with origin AS269357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269357 in the RIR database for the space.669 of 673
ROA: none45.185.47.0/24No ROA covers it. Add a ROA for AS269357, maxLength 24.2 of 673
Route object: none45.185.47.0/24No route object for it. A route object for 45.185.44.0/22 with origin AS269357 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269357 in the RIR database for the space.2 of 673

Route objects not announced

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

45.185.44.0/22RADBNo ROA
2804:6360::/32RADBNo 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.