bgpreport

Network · data from 2026-11-12

AS269172 AS269172 - JCM NET TELECOM LTDA

Registry name: AS269172 - JCM NET TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269172, 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.
2804:6084::/40 Valid Nonecovered by 2804:6084::/32 630 99% 67
2804:6084:100::/40 Valid Nonecovered by 2804:6084::/32 630 99% 67
2804:6084:200::/40 Valid Nonecovered by 2804:6084::/32 630 99% 67
45.181.53.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
45.181.54.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
45.181.52.0/24 Valid Other IRR onlyTC 671 100% 66
45.181.54.0/24 Valid Other IRR onlyTC 671 100% 66
45.181.55.0/24 Valid Other IRR onlyTC 671 100% 66
2804:6084::/32 Valid Other IRR onlyRADB, TC 632 99% 67

AS-SET

AS269172 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 11 are in fix.csv.

  • Route object: none3
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2804:6084::/40No route object for it. A route object for 2804:6084::/32 with origin AS269172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269172 in the RIR database for the space.630 of 636
Route object: none2804:6084:100::/40No route object for it. A route object for 2804:6084::/32 with origin AS269172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269172 in the RIR database for the space.630 of 636
Route object: none2804:6084:200::/40No route object for it. A route object for 2804:6084::/32 with origin AS269172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269172 in the RIR database for the space.630 of 636
Route object: RIR45.181.53.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.181.54.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.181.52.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.181.54.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.181.55.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:6084::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

45.181.52.0/22RADB, TCNo ROA
45.181.52.0/23RADBNo 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.