Network · data from 2026-11-12
AS49895 DCENTER.PL
Registry name: DCENTER-AS dcenter.pl sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49895, 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.
| 213.5.12.0/24 | Valid | Other origin onlycovered by 213.5.8.0/21 | 668 99% |
| 213.5.13.0/24 | Valid | Other origin onlycovered by 213.5.8.0/21 | 668 99% |
| 213.5.14.0/24 | Valid | Other origin onlycovered by 213.5.8.0/21 | 668 99% |
| 213.5.15.0/24 | Valid | Other origin onlycovered by 213.5.8.0/21 | 668 99% |
| 46.254.75.0/24 | Valid | Other origin onlycovered by 46.254.72.0/22 | 667 99% |
| 213.5.8.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 46.254.72.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 213.5.8.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 213.5.9.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 213.5.10.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 213.5.11.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.254.72.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.254.73.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.254.74.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.254.76.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 46.254.79.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a00:e800::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS49895: AS-DCENTER. 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 (AS49895 isn't in the set, or no route object for AS49895 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 | AS49895 in it | Not covered |
|---|---|---|---|---|---|
| AS-DCENTER | RIPElists itself further down | 162 | 42 | 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 7 are in fix.csv.
- Route object: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 213.5.12.0/24 | Route objects for it name AS44655. A route object for 213.5.8.0/21 with origin AS49895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49895 in the RIR database for the space. |
| Route object: none | 213.5.13.0/24 | Route objects for it name AS44655. A route object for 213.5.8.0/21 with origin AS49895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49895 in the RIR database for the space. |
| Route object: none | 213.5.14.0/24 | Route objects for it name AS44655. A route object for 213.5.8.0/21 with origin AS49895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49895 in the RIR database for the space. |
| Route object: none | 213.5.15.0/24 | Route objects for it name AS44655. A route object for 213.5.8.0/21 with origin AS49895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49895 in the RIR database for the space. |
| Route object: none | 46.254.75.0/24 | Route objects for it name AS44655. A route object for 46.254.72.0/22 with origin AS49895 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49895 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49895 whose prefix no peer sees AS49895 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.5.8.0/22 | RIPE | Invalid: maxLength |
| 2a00:e800::/29 | 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.