bgpreport

Network · data from 2026-11-12

AS269306 AS269306 - ULTRANET SERVICOS DE COMUNICACAO

Registry name: AS269306 - ULTRANET SERVICOS DE COMUNICACAO, BR · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 20.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 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS269306, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS269306, 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.183.192.0/24 No ROA Nonecovered by 45.183.192.0/22 669 99% 67
45.183.193.0/24 No ROA Nonecovered by 45.183.192.0/22 669 99% 67
45.183.195.0/24 No ROA Nonecovered by 45.183.192.0/22 669 99% 67
45.183.194.0/24 No ROA Nonecovered by 45.183.192.0/22 667 99% 67
2804:6298:fc00::/39 No ROA Nonecovered by 2804:6298::/32 631 99% 68
45.183.192.0/22 No ROA Other IRR onlyRADB 665 99% 67
2804:6298::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS269306 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.183.192.0/24No ROA covers it. Add a ROA for AS269306, maxLength 24.669 of 673
Route object: none45.183.192.0/24No route object for it. A route object for 45.183.192.0/22 with origin AS269306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269306 in the RIR database for the space.669 of 673
ROA: none45.183.193.0/24No ROA covers it. Add a ROA for AS269306, maxLength 24.669 of 673
Route object: none45.183.193.0/24No route object for it. A route object for 45.183.192.0/22 with origin AS269306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269306 in the RIR database for the space.669 of 673
ROA: none45.183.195.0/24No ROA covers it. Add a ROA for AS269306, maxLength 24.669 of 673
Route object: none45.183.195.0/24No route object for it. A route object for 45.183.192.0/22 with origin AS269306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269306 in the RIR database for the space.669 of 673
ROA: none45.183.194.0/24No ROA covers it. Add a ROA for AS269306, maxLength 24.667 of 673
Route object: none45.183.194.0/24No route object for it. A route object for 45.183.192.0/22 with origin AS269306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269306 in the RIR database for the space.667 of 673
ROA: none2804:6298:fc00::/39No ROA covers it. Add a ROA for AS269306, maxLength 39.631 of 636
Route object: none2804:6298:fc00::/39No route object for it. A route object for 2804:6298::/32 with origin AS269306 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269306 in the RIR database for the space.631 of 636
ROA: none45.183.192.0/22No ROA covers it. Add a ROA for AS269306, maxLength 22.665 of 673
Route object: RIR45.183.192.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:6298::/32No ROA covers it. Add a ROA for AS269306, maxLength 32.636 of 636
Route object: RIR2804:6298::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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