bgpreport

Network · data from 2026-11-12

AS268798 AS268798 - JG TELECOM

Registry name: AS268798 - JG TELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268798, 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.171.140.0/24 Valid Other IRR onlyRADB 672 100% 67
45.171.141.0/24 Valid Other IRR onlyRADB 672 100% 67
45.171.143.0/24 Valid Other IRR onlyALTDB, RADB 663 99% 67
2804:5ad0::/32 Valid Other IRR onlyALTDB, RADB 634 100% 69
2804:5ad0::/33 Valid Other IRR onlyRADB 630 99% 69

AS-SET

AS268798 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 39 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced34
ChangePrefix or setDetailFull-table peers
Route object: RIR45.171.140.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.171.141.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR45.171.143.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:5ad0::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:5ad0::/33Route object only in RADB. Add it in the RIR database for the space.630 of 636

Route objects not announced

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

45.171.140.0/22ALTDB, RADBValid
45.171.140.0/23ALTDB, RADBValid
45.171.142.0/23ALTDB, RADBValid
45.171.142.0/24ALTDB, RADBValid
2804:40c0::/32ALTDBNo ROA
2804:5ad0::/34RADBValid
2804:5ad0::/35RADBValid
2804:5ad0::/36RADBValid
2804:5ad0:1000::/36RADBValid
2804:5ad0:2000::/35RADBValid
2804:5ad0:2000::/36RADBValid
2804:5ad0:3000::/36RADBValid
2804:5ad0:4000::/34RADBValid
2804:5ad0:4000::/35RADBValid
2804:5ad0:4000::/36RADBValid
2804:5ad0:5000::/36RADBValid
2804:5ad0:6000::/35RADBValid
2804:5ad0:6000::/36RADBValid
2804:5ad0:7000::/36RADBValid
2804:5ad0:8000::/33RADBValid
2804:5ad0:8000::/34RADBValid
2804:5ad0:8000::/35RADBValid
2804:5ad0:8000::/36RADBValid
2804:5ad0:9000::/36RADBValid
2804:5ad0:a000::/35RADBValid
2804:5ad0:a000::/36RADBValid
2804:5ad0:b000::/36RADBValid
2804:5ad0:c000::/34RADBValid
2804:5ad0:c000::/35RADBValid
2804:5ad0:c000::/36RADBValid
2804:5ad0:d000::/36RADBValid
2804:5ad0:e000::/35RADBValid
2804:5ad0:e000::/36RADBValid
2804:5ad0:f000::/36ALTDB, RADBValid

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.