Network · data from 2026-11-12
AS34450 NET GATE COMUNICATII
Registry name: WDC-AS Net Gate Telecom S.R.L., RO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34450, 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.
| 89.18.24.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 89.40.232.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.102.156.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 185.102.157.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 188.241.209.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 89.43.50.0/24 | No ROA | RIR databaseRIPE | 664 99% |
| 113.203.209.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 113.203.219.0/24 | Valid | RIR databaseAPNIC | 671 100% |
| 188.215.72.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.215.73.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 85.204.125.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 86.106.104.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 89.34.8.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 89.43.46.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 93.114.171.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 188.213.18.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 188.215.95.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 93.114.55.0/24 | Valid | RIR databaseRIPE | 666 99% |
| 89.37.136.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 89.44.209.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 89.45.34.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 93.114.99.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 93.114.187.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 2a05:b680:1::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS34450: AS-WDCNET-NEW. 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 (AS34450 isn't in the set, or no route object for AS34450 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 | AS34450 in it | Not covered |
|---|---|---|---|---|---|
| AS-WDCNET-NEW | RIPE | 13 | 4 | 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 12 are in fix.csv.
- ROA: none6
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.18.24.0/24 | No ROA covers it. Add a ROA for AS34450, maxLength 24. |
| ROA: none | 89.40.232.0/24 | No ROA covers it. Add a ROA for AS34450, maxLength 24. |
| ROA: none | 185.102.156.0/24 | No ROA covers it. Add a ROA for AS34450, maxLength 24. |
| ROA: none | 185.102.157.0/24 | No ROA covers it. Add a ROA for AS34450, maxLength 24. |
| ROA: none | 188.241.209.0/24 | No ROA covers it. Add a ROA for AS34450, maxLength 24. |
| ROA: none | 89.43.50.0/24 | No ROA covers it. Add a ROA for AS34450, maxLength 24. |
Route objects not announced
Route objects with origin AS34450 whose prefix no peer sees AS34450 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.18.16.0/21 | RIPE | No ROA |
| 89.18.16.0/22 | RIPE | No ROA |
| 89.18.20.0/22 | RIPE | No ROA |
| 102.135.30.0/24 | AFRINIC | Invalid: origin |
| 195.178.148.0/23 | RIPE | No ROA |
| 212.111.200.0/24 | RIPE | Invalid: origin |
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.