Network · data from 2026-11-12
AS264993 NETLIDERES - PROVEDOR DE INTERNET EIRELI
Registry name: AS264993 - NETLIDERES - PROVEDOR DE INTERNET EIRELI, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264993, 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.
| 170.84.116.0/24 | Valid | Nonecovered by 170.84.116.0/23 | 672 100% |
| 170.84.117.0/24 | Valid | Nonecovered by 170.84.116.0/23 | 672 100% |
| 170.84.116.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 170.84.119.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 2804:311c::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:311c::/33 | Valid | Other IRR onlyTC | 8 1%low visibility |
| 2804:311c:8000::/33 | Valid | Other IRR onlyTC | 8 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS264993: TC::AS264993:AS-ANNOUNCEMENTS. 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 (AS264993 isn't in the set, or no route object for AS264993 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 | AS264993 in it | Not covered |
|---|---|---|---|---|---|
| TC::AS264993:AS-ANNOUNCEMENTS | TC | 2 | 2 | Yes | 0 |
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 10 are in fix.csv.
- Route object: none2
- Route object: RIR5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 170.84.116.0/24 | No route object for it. A route object for 170.84.116.0/23 with origin AS264993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264993 in the RIR database for the space. |
| Route object: none | 170.84.117.0/24 | No route object for it. A route object for 170.84.116.0/23 with origin AS264993 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264993 in the RIR database for the space. |
| Route object: RIR | 170.84.116.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 170.84.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:311c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:311c::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:311c:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264993 whose prefix no peer sees AS264993 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.84.116.0/23 | TC | Valid |
| 170.84.118.0/23 | TC | Valid |
| 170.84.118.0/24 | RADB | Valid |
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.