Network · data from 2026-11-12
AS263995 LINK BRASIL
Registry name: AS263995 - LINK BRASIL LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263995, 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.
| 138.255.230.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 138.255.231.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 138.255.228.0/24 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 138.255.229.0/24 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 2804:2910:10::/44 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:2910::/44 | Valid | Other IRR onlyTC | 631 99% |
| 2804:2910:20::/44 | Valid | Other IRR onlyTC | 631 99% |
| 2804:2910:8000::/44 | Valid | Other IRR onlyRADB, TC | 631 99% |
AS-SET
PeeringDB's irr_as_set for AS263995: AS-GLOBAL. 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 (AS263995 isn't in the set, or no route object for AS263995 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 | AS263995 in it | Not covered |
|---|---|---|---|---|---|
| AS-GLOBAL | RIPElists itself further down3 member sets in no database: AS-INTERNETONE_CH, AS44477:AS-DOWNSTREAMS, AS48977:AS-STEPCOM | 522 | 106 | No | 8 |
| ARIN (also)2 member sets in no database: AS-ERICNET:AS-NYC, AS50833:AS-FIBERTELECOM | 86 | 35 | No | 8 |
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 17 are in fix.csv.
- Route object: RIR8
- AS-SET: own ASN1
- AS-SET: missing member3
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 138.255.230.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.231.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.228.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.255.229.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2910:10::/44 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2910::/44 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2910:20::/44 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2910:8000::/44 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS-GLOBAL | AS263995 isn't in AS-GLOBAL (RIPE) once expanded. Add AS263995 to it. |
| AS-SET: missing member | AS-GLOBAL | AS-GLOBAL (RIPE) lists AS-INTERNETONE_CH; no IRR database read has it. |
| AS-SET: missing member | AS-GLOBAL | AS-GLOBAL (RIPE) lists AS44477:AS-DOWNSTREAMS; no IRR database read has it. |
| AS-SET: missing member | AS-GLOBAL | AS-GLOBAL (RIPE) lists AS48977:AS-STEPCOM; no IRR database read has it. |
Route objects not announced
Route objects with origin AS263995 whose prefix no peer sees AS263995 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.255.228.0/22 | RADB, TC | No ROA |
| 138.255.228.0/23 | RADB, TC | No ROA |
| 138.255.230.0/23 | TC | No ROA |
| 2804:2910::/32 | RADB, TC | No ROA |
| 2804:2910:a0::/48 | RADB | No ROA |
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.