Network · data from 2026-11-12
AS272215 Tribunal Regional do Trabalho da 18 Regiao
Registry name: AS272215 - Tribunal Regional do Trabalho da 18a Regiao, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272215, 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.
| 2801:80:3ee0::/48 | No ROA | Other IRR onlyRADB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS272215: AS-TRT18. 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 (AS272215 isn't in the set, or no route object for AS272215 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.
| Name | Database | ASNs | Sets | AS272215 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-TRT18 | In no IRR database read today. | |||||
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 3 are in fix.csv.
- ROA: none1
- Route object: RIR1
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2801:80:3ee0::/48 | No ROA covers it. Add a ROA for AS272215, maxLength 48. |
| Route object: RIR | 2801:80:3ee0::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS-TRT18 | PeeringDB names AS-TRT18; no IRR database read has it. |
Route objects not announced
Every route object with origin AS272215 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.