bgpreport

Network · data from 2026-11-12

AS267264 JrFiber Telecomunicações

Registry name: AS267264 - Jrfiber servicos de comunicacao, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267264, 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.232.124.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
2804:4acc::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
45.232.124.0/24 No ROA Other IRR onlyRADB, TC 3 0%low visibility 4
45.232.125.0/24 No ROA Other IRR onlyRADB, TC 3 0%low visibility 4
45.232.126.0/24 No ROA Other IRR onlyRADB, TC 3 0%low visibility 4
45.232.127.0/24 No ROA Other IRR onlyRADB, TC 2 0%low visibility 2
2804:4acc::/34 No ROA Other IRR onlyRADB 1 0%low visibility 2
2804:4acc:4000::/34 No ROA Other IRR onlyRADB 1 0%low visibility 2
2804:4acc:8000::/34 No ROA Other IRR onlyRADB 1 0%low visibility 2
2804:4acc:c000::/34 No ROA Other IRR onlyRADB 1 0%low visibility 2

AS-SET

AS267264'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 24 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none45.232.124.0/22No ROA covers it. Add a ROA for AS267264, maxLength 22.671 of 673
Route object: RIR45.232.124.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none2804:4acc::/32No ROA covers it. Add a ROA for AS267264, maxLength 32.633 of 636
Route object: RIR2804:4acc::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none45.232.124.0/24No ROA covers it. Add a ROA for AS267264, maxLength 24.3 of 673
Route object: RIR45.232.124.0/24Route object only in RADB, TC. Add it in the RIR database for the space.3 of 673
ROA: none45.232.125.0/24No ROA covers it. Add a ROA for AS267264, maxLength 24.3 of 673
Route object: RIR45.232.125.0/24Route object only in RADB, TC. Add it in the RIR database for the space.3 of 673
ROA: none45.232.126.0/24No ROA covers it. Add a ROA for AS267264, maxLength 24.3 of 673
Route object: RIR45.232.126.0/24Route object only in RADB, TC. Add it in the RIR database for the space.3 of 673
ROA: none45.232.127.0/24No ROA covers it. Add a ROA for AS267264, maxLength 24.2 of 673
Route object: RIR45.232.127.0/24Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
ROA: none2804:4acc::/34No ROA covers it. Add a ROA for AS267264, maxLength 34.1 of 636
Route object: RIR2804:4acc::/34Route object only in RADB. Add it in the RIR database for the space.1 of 636
ROA: none2804:4acc:4000::/34No ROA covers it. Add a ROA for AS267264, maxLength 34.1 of 636
Route object: RIR2804:4acc:4000::/34Route object only in RADB. Add it in the RIR database for the space.1 of 636
ROA: none2804:4acc:8000::/34No ROA covers it. Add a ROA for AS267264, maxLength 34.1 of 636
Route object: RIR2804:4acc:8000::/34Route object only in RADB. Add it in the RIR database for the space.1 of 636
ROA: none2804:4acc:c000::/34No ROA covers it. Add a ROA for AS267264, maxLength 34.1 of 636
Route object: RIR2804:4acc:c000::/34Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

45.232.124.0/23RADB, TCNo ROA
45.232.126.0/23RADB, TCNo ROA
2804:4acc::/33RADB, TCNo ROA
2804:4acc:8000::/33RADB, TCNo 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.