Network · data from 2026-11-12
AS34087 NTE Telekom AS
Registry name: NTE-BREDBAND NTE TELEKOM AS, NO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34087, 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.
| 185.161.56.0/24 | Invalid: maxLength | Nonecovered by 185.161.56.0/22 | 19 3%low visibility |
| 185.161.57.0/24 | Invalid: maxLength | Nonecovered by 185.161.56.0/22 | 19 3%low visibility |
| 84.16.197.128/26 | Invalid: maxLength | Nonecovered by 84.16.192.0/19 | 2 0%low visibility |
| 185.161.57.128/28 | Invalid: maxLength | Nonecovered by 185.161.56.0/22 | 2 0%low visibility |
| 185.161.57.208/28 | Invalid: maxLength | Nonecovered by 185.161.56.0/22 | 2 0%low visibility |
| 185.161.57.224/28 | Invalid: maxLength | Nonecovered by 185.161.56.0/22 | 2 0%low visibility |
| 178.164.64.0/19 | Valid | Nonecovered by 178.164.0.0/17 | 672 100% |
| 2a01:560::/32 | Valid | Nonecovered by 2a01:560::/29 | 635 100% |
| 84.16.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 185.161.56.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.168.80.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 89.151.224.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 152.65.32.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 152.65.96.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 178.164.0.0/17 | Valid | RIR databaseRIPE | 672 100% |
| 178.164.0.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 84.52.192.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 84.52.224.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 85.89.0.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 89.151.192.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 94.246.0.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 148.252.64.0/18 | Valid | RIR databaseRIPE | 671 100% |
| 148.252.64.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 148.252.96.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 152.65.0.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 152.65.64.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 178.164.32.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 178.164.96.0/19 | Valid | RIR databaseRIPE | 671 100% |
| 2001:678:464::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:560::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS34087: AS-NTE. 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 (AS34087 isn't in the set, or no route object for AS34087 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 | AS34087 in it | Not covered |
|---|---|---|---|---|---|
| AS-NTE | RIPElists itself further down3 member sets in no database: AS204829:AS-ALL, AS209861:AS-ALL, AS213733:AS-HACK-FO | 658 | 265 | Yes | 4 |
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 19 are in fix.csv.
- ROA: maxLength6
- Route object: none8
- AS-SET: missing member3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.161.56.0/24 | ROA 185.161.56.0/22 AS34087 has maxLength 22; ROA 185.161.56.0/23 AS34087 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 185.161.56.0/24. |
| Route object: none | 185.161.56.0/24 | No route object for it. A route object for 185.161.56.0/22 with origin AS34087 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34087 in the RIR database for the space. |
| ROA: maxLength | 185.161.57.0/24 | ROA 185.161.56.0/22 AS34087 has maxLength 22; ROA 185.161.56.0/23 AS34087 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 185.161.57.0/24. |
| Route object: none | 185.161.57.0/24 | No route object for it. A route object for 185.161.56.0/22 with origin AS34087 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34087 in the RIR database for the space. |
| ROA: maxLength | 84.16.197.128/26 | ROA 84.16.192.0/19 AS34087 has maxLength 19; the route is a /26. Raise the maxLength, or add a ROA for 84.16.197.128/26. |
| Route object: none | 84.16.197.128/26 | No route object for it. A route object for 84.16.192.0/19 with origin AS34087 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34087 in the RIR database for the space. |
| ROA: maxLength | 185.161.57.128/28 | ROA 185.161.56.0/22 AS34087 has maxLength 22; ROA 185.161.56.0/23 AS34087 has maxLength 23; the route is a /28. Raise the maxLength, or add a ROA for 185.161.57.128/28. |
| Route object: none | 185.161.57.128/28 | No route object for it. A route object for 185.161.56.0/22 with origin AS34087 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34087 in the RIR database for the space. |
| ROA: maxLength | 185.161.57.208/28 | ROA 185.161.56.0/22 AS34087 has maxLength 22; ROA 185.161.56.0/23 AS34087 has maxLength 23; the route is a /28. Raise the maxLength, or add a ROA for 185.161.57.208/28. |
| Route object: none | 185.161.57.208/28 | No route object for it. A route object for 185.161.56.0/22 with origin AS34087 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34087 in the RIR database for the space. |
| ROA: maxLength | 185.161.57.224/28 | ROA 185.161.56.0/22 AS34087 has maxLength 22; ROA 185.161.56.0/23 AS34087 has maxLength 23; the route is a /28. Raise the maxLength, or add a ROA for 185.161.57.224/28. |
| Route object: none | 185.161.57.224/28 | No route object for it. A route object for 185.161.56.0/22 with origin AS34087 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34087 in the RIR database for the space. |
| Route object: none | 178.164.64.0/19 | No route object for it. A route object for 178.164.0.0/17 with origin AS34087 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34087 in the RIR database for the space. |
| Route object: none | 2a01:560::/32 | No route object for it. A route object for 2a01:560::/29 with origin AS34087 covers it (filters allowing more-specifics accept it). Add a route object with origin AS34087 in the RIR database for the space. |
| AS-SET: missing member | AS-NTE | AS-NTE (RIPE) lists AS204829:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-NTE | AS-NTE (RIPE) lists AS209861:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-NTE | AS-NTE (RIPE) lists AS213733:AS-HACK-FO; no IRR database read has it. |
Route objects not announced
Route objects with origin AS34087 whose prefix no peer sees AS34087 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.151.192.0/18 | RIPE | No ROA |
| 152.65.0.0/17 | RIPE | 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.