Network · data from 2026-11-12
AS205988 Playco Entertainment
Registry name: PLAYCO-AS Playco Entertainment FZ LLC, AE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205988, 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.200.53.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a0a:ab40:1::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS205988: as-playco. 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 (AS205988 isn't in the set, or no route object for AS205988 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 | AS205988 in it | Not covered |
|---|---|---|---|---|---|
| as-playco | RIPE | 1 | 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 7 are in fix.csv.
- Route object: not announced7
Route objects not announced
Route objects with origin AS205988 whose prefix no peer sees AS205988 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.200.52.0/22 | RADB, RIPE | Valid |
| 185.200.52.0/24 | RIPE | Valid |
| 185.200.54.0/24 | RADB, RIPE | Valid |
| 185.200.55.0/24 | RIPE | Valid |
| 2a0a:ab40::/29 | RIPE | Valid |
| 2a0a:ab40::/48 | RADB, RIPE | Valid |
| 2a0a:ab40:2::/48 | RADB, RIPE | 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.