Network · data from 2026-11-12
AS20783 pop-interactive GmbH
Registry name: POP pop-interactive GmbH, DE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20783, 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.
| 212.79.0.0/18 | No ROA | RIR databaseRIPE | 673 100% |
| 2001:1b30::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 2001:1b30::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 195.222.192.0/18 | No ROA | RIR databaseRIPE | 2 0%low visibility |
| 212.79.57.0/24 | Valid | Nonecovered by 212.79.0.0/18 | 653 97% |
| 195.222.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.222.200.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.222.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.222.248.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 195.222.216.0/21 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.222.224.0/21 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.222.232.0/21 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 195.222.240.0/21 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS20783: AS-POP. 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 (AS20783 isn't in the set, or no route object for AS20783 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 | AS20783 in it | Not covered |
|---|---|---|---|---|---|
| AS-POP | RIPE | 3 | 1 | 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 9 are in fix.csv.
- ROA: none4
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 212.79.0.0/18 | No ROA covers it. Add a ROA for AS20783, maxLength 18. |
| ROA: none | 2001:1b30::/32 | No ROA covers it. Add a ROA for AS20783, maxLength 32. |
| ROA: none | 2001:1b30::/29 | No ROA covers it. Add a ROA for AS20783, maxLength 29. |
| ROA: none | 195.222.192.0/18 | No ROA covers it. Add a ROA for AS20783, maxLength 18. |
| Route object: none | 212.79.57.0/24 | No route object for it. A route object for 212.79.0.0/18 with origin AS20783 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20783 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS20783 whose prefix no peer sees AS20783 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.27.46.0/24 | RIPE | No ROA |
| 212.79.0.0/24 | RIPE | No ROA |
| 212.79.1.0/24 | RIPE | No ROA |
| 212.79.2.0/24 | 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.