Network · data from 2026-11-12
AS270707 LINK NET BRASIL TELECOMUNICAÇÕES LTDA
Registry name: AS270707 - LINK NET BRASIL TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270707, 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.
| 2804:7020:8100::/40 | No ROA | Other IRR onlyRADB | 633 100% |
| 189.127.157.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 189.127.159.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 189.127.158.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 189.127.156.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 2804:7020::/33 | Valid | Other IRR onlyRADB | 634 100% |
| 2804:7020:8200::/40 | Valid | Other IRR onlyRADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS270707: AS270707. 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 (AS270707 isn't in the set, or no route object for AS270707 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 | AS270707 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS270707 | A single AS number, not a set: AS270707 (this network), 12 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 13 are in fix.csv.
- ROA: none1
- Route object: RIR7
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:7020:8100::/40 | No ROA covers it. Add a ROA for AS270707, maxLength 40. |
| Route object: RIR | 2804:7020:8100::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.127.157.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.127.159.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.127.158.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.127.156.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7020::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7020:8200::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270707 whose prefix no peer sees AS270707 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 189.127.156.0/22 | RADB, TC | No ROA |
| 189.127.156.0/23 | RADB | No ROA |
| 189.127.158.0/23 | RADB | No ROA |
| 2804:7020::/32 | NTTCOM, RADB, TC | No ROA |
| 2804:7020:8000::/33 | 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.