bgpreport

Network · data from 2026-11-12

AS269252 Jato64 Telecomunicações

Registry name: AS269252 - INFORTEL SERVICOS LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269252, 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.181.220.0/22 No ROA Other IRR onlyRADB 665 99% 67
45.181.220.0/23 No ROA Other IRR onlyRADB 665 99% 67
45.181.222.0/23 No ROA Other IRR onlyRADB 665 99% 67
2804:61b8::/32 No ROA Other IRR onlyRADB 636 100% 67
186.196.28.0/22 Valid Other IRR onlyRADB 665 99% 67
186.196.28.0/23 Valid Other IRR onlyRADB 665 99% 67
186.196.28.0/24 Valid Other IRR onlyRADB 665 99% 67
186.196.29.0/24 Valid Other IRR onlyRADB 665 99% 67
186.196.30.0/23 Valid Other IRR onlyRADB 665 99% 67
186.196.30.0/24 Valid Other IRR onlyRADB 665 99% 67
186.196.31.0/24 Valid Other IRR onlyRADB 665 99% 67

AS-SET

AS269252'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 19 are in fix.csv.

  • ROA: none4
  • Route object: RIR11
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.181.220.0/22No ROA covers it. Add a ROA for AS269252, maxLength 22.665 of 673
Route object: RIR45.181.220.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none45.181.220.0/23No ROA covers it. Add a ROA for AS269252, maxLength 23.665 of 673
Route object: RIR45.181.220.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none45.181.222.0/23No ROA covers it. Add a ROA for AS269252, maxLength 23.665 of 673
Route object: RIR45.181.222.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2804:61b8::/32No ROA covers it. Add a ROA for AS269252, maxLength 32.636 of 636
Route object: RIR2804:61b8::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR186.196.28.0/22Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.196.28.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.196.28.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.196.29.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.196.30.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.196.30.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR186.196.31.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673

Route objects not announced

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

45.181.220.0/24RADBNo ROA
45.181.221.0/24RADBNo ROA
45.181.222.0/24RADBNo ROA
45.181.223.0/24RADBNo 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.