bgpreport

Network · data from 2026-11-12

AS263261 TRT3

Registry name: AS263261 - TRIBUNAL REGIONAL DO TRABALHO DA 3A REGIAO, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263261, 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.
192.100.177.0/24 No ROA Other IRR onlyALTDB 671 100% 67
2801:80:2600::/40 No ROA Other IRR onlyALTDB 636 100% 67
2801:80:2600::/41 No ROA Other IRR onlyALTDB 636 100% 67
2801:80:2680::/41 No ROA Other IRR onlyALTDB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS263261: AS263261:RS-ROUTES. 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 (AS263261 isn't in the set, or no route object for AS263261 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 objectsAS263261 in itNot covered
AS263261:RS-ROUTES A route-set, not an AS-SET; route-sets aren't expanded.

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.

  • ROA: none4
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none192.100.177.0/24No ROA covers it. Add a ROA for AS263261, maxLength 24.671 of 673
Route object: RIR192.100.177.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none2801:80:2600::/40No ROA covers it. Add a ROA for AS263261, maxLength 40.636 of 636
Route object: RIR2801:80:2600::/40Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
ROA: none2801:80:2600::/41No ROA covers it. Add a ROA for AS263261, maxLength 41.636 of 636
Route object: RIR2801:80:2600::/41Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
ROA: none2801:80:2680::/41No ROA covers it. Add a ROA for AS263261, maxLength 41.635 of 636
Route object: RIR2801:80:2680::/41Route object only in ALTDB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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