bgpreport

Network · data from 2026-11-12

AS265078 JHS TELECOMUNICAÇOES

Registry name: AS265078 - JHS TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265078, 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.
170.233.113.0/24 Valid Nonecovered by 170.233.112.0/23 175 26% 51
170.233.112.0/22 Valid Other IRR onlyALTDB 672 100% 67
170.233.112.0/23 Valid Other IRR onlyALTDB 672 100% 67
170.233.114.0/23 Valid Other IRR onlyALTDB 672 100% 67
2804:3270::/32 Valid Other IRR onlyALTDB 632 99% 69
170.233.112.0/24 Valid Other IRR onlyALTDB 176 26% 51
170.233.114.0/24 Valid Other IRR onlyALTDB 176 26% 51
170.233.115.0/24 Valid Other IRR onlyALTDB 176 26% 51

AS-SET

PeeringDB's irr_as_set for AS265078: AS-265078. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS265078 isn't in the set, or no route object for AS265078 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS265078 in itNot covered
AS-265078 ALTDB 154207 Yes 0

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

  • Route object: none1
  • Route object: RIR7
ChangePrefix or setDetailFull-table peers
Route object: none170.233.113.0/24No route object for it. A route object for 170.233.112.0/23 with origin AS265078 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265078 in the RIR database for the space.175 of 673
Route object: RIR170.233.112.0/22Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.233.112.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR170.233.114.0/23Route object only in ALTDB. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:3270::/32Route object only in ALTDB. Add it in the RIR database for the space.632 of 636
Route object: RIR170.233.112.0/24Route object only in ALTDB. Add it in the RIR database for the space.176 of 673
Route object: RIR170.233.114.0/24Route object only in ALTDB. Add it in the RIR database for the space.176 of 673
Route object: RIR170.233.115.0/24Route object only in ALTDB. Add it in the RIR database for the space.176 of 673

Route objects not announced

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