bgpreport

Network · data from 2026-11-12

AS270581 JET NETWORK

Registry name: AS270581 - JET NETWORK TELECOMUNICACAO LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
5IPv6 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
2Route objects not announced registered with origin AS270581, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270581, 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.
177.8.132.0/22 Valid Other IRR onlyTC 672 100% 67
177.8.134.0/23 Valid Other IRR onlyTC 667 99% 67
177.8.132.0/23 Valid Other IRR onlyTC 665 99% 67
2804:6e30::/32 Valid Other IRR onlyTC 633 100% 67
177.8.132.0/24 Valid Other IRR onlyTC 67 10%low visibility 25
177.8.134.0/24 Valid Other IRR onlyTC 67 10%low visibility 25
177.8.135.0/24 Valid Other IRR onlyTC 67 10%low visibility 25
177.8.133.0/24 Valid Other IRR onlyTC 66 10%low visibility 25
2804:6e30::/34 Valid Other IRR onlyTC 54 8%low visibility 23
2804:6e30:4000::/34 Valid Other IRR onlyTC 54 8%low visibility 23
2804:6e30:8000::/34 Valid Other IRR onlyTC 54 8%low visibility 23
2804:6e30:c000::/34 Valid Other IRR onlyTC 54 8%low visibility 23

AS-SET

PeeringDB's irr_as_set for AS270581: AS270581. 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 (AS270581 isn't in the set, or no route object for AS270581 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 objectsAS270581 in itNot covered
AS270581 A single AS number, not a set: AS270581 (this network), 14 route objects.

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: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR177.8.132.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.8.134.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.8.132.0/23Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:6e30::/32Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR177.8.132.0/24Route object only in TC. Add it in the RIR database for the space.67 of 673
Route object: RIR177.8.134.0/24Route object only in TC. Add it in the RIR database for the space.67 of 673
Route object: RIR177.8.135.0/24Route object only in TC. Add it in the RIR database for the space.67 of 673
Route object: RIR177.8.133.0/24Route object only in TC. Add it in the RIR database for the space.66 of 673
Route object: RIR2804:6e30::/34Route object only in TC. Add it in the RIR database for the space.54 of 636
Route object: RIR2804:6e30:4000::/34Route object only in TC. Add it in the RIR database for the space.54 of 636
Route object: RIR2804:6e30:8000::/34Route object only in TC. Add it in the RIR database for the space.54 of 636
Route object: RIR2804:6e30:c000::/34Route object only in TC. Add it in the RIR database for the space.54 of 636

Route objects not announced

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

2804:6e30::/33TCValid
2804:6e30:8000::/33TCValid

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.