bgpreport

Network · data from 2026-11-12

AS265424 Horizontes Telecom

Registry name: AS265424 - Horizontes Telecom LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
8Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS265424, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265424, 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.

168.195.24.0/23 Valid Other IRR onlyALTDB 671 100% 67
168.195.26.0/23 Valid Other IRR onlyALTDB 671 100% 67
168.195.24.0/22 Valid Other IRR onlyALTDB, RADB 663 99% 67
2804:33e8::/33 Valid Other IRR onlyALTDB 636 100% 67
2804:33e8:8000::/33 Valid Other IRR onlyALTDB 636 100% 67
2804:33e8::/32 Valid Other IRR onlyALTDB, RADB 630 99% 69
168.195.24.0/24 Valid Other IRR onlyALTDB, RADB 9 1%low visibility 5
168.195.25.0/24 Valid Other IRR onlyALTDB, RADB 9 1%low visibility 5
168.195.26.0/24 Valid Other IRR onlyALTDB, RADB 9 1%low visibility 5
168.195.27.0/24 Valid Other IRR onlyALTDB, RADB 9 1%low visibility 5
2804:33e8::/34 Valid Other IRR onlyALTDB 9 1%low visibility 5
2804:33e8:4000::/34 Valid Other IRR onlyALTDB 9 1%low visibility 5
2804:33e8:8000::/34 Valid Other IRR onlyALTDB 9 1%low visibility 5
2804:33e8:c000::/34 Valid Other IRR onlyALTDB 9 1%low visibility 5

AS-SET

PeeringDB's irr_as_set for AS265424: AS-HORIZONTES. 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 (AS265424 isn't in the set, or no route object for AS265424 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 objectsAS265424 in itNot covered
AS-HORIZONTES ALTDB 1114 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 14 are in fix.csv.

  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR168.195.24.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.195.26.0/23Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
Route object: RIR168.195.24.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.663 of 673
Route object: RIR2804:33e8::/33Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:33e8:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:33e8::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.630 of 636
Route object: RIR168.195.24.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.9 of 673
Route object: RIR168.195.25.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.9 of 673
Route object: RIR168.195.26.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.9 of 673
Route object: RIR168.195.27.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.9 of 673
Route object: RIR2804:33e8::/34Route object only in ALTDB. Add it in the RIR database for the space.9 of 636
Route object: RIR2804:33e8:4000::/34Route object only in ALTDB. Add it in the RIR database for the space.9 of 636
Route object: RIR2804:33e8:8000::/34Route object only in ALTDB. Add it in the RIR database for the space.9 of 636
Route object: RIR2804:33e8:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.9 of 636

Route objects not announced

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