Network · data from 2026-11-12
AS213529 Sculk Ltd
Registry name: SCULK-AS Sculk Ltd., GB · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213529, 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.
| 147.45.216.0/24 | Valid | None | 671 100% |
| 2a0d:d940:20::/44 | Valid | None | 634 100% |
| 23.26.37.0/24 | Valid | RIR databaseARIN | 671 100% |
| 23.26.193.0/24 | Valid | RIR databaseARIN | 671 100% |
| 31.76.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 31.77.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 50.114.58.0/24 | Valid | RIR databaseARIN | 671 100% |
| 50.114.102.0/24 | Valid | RIR databaseARIN | 671 100% |
| 50.114.115.0/24 | Valid | RIR databaseARIN | 671 100% |
| 88.210.63.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 96.126.129.0/24 | Valid | RIR databaseARIN | 671 100% |
| 108.165.32.0/23 | Valid | RIR databaseARIN | 671 100% |
| 108.165.173.0/24 | Valid | RIR databaseARIN | 671 100% |
| 108.165.174.0/24 | Valid | RIR databaseARIN | 671 100% |
| 108.165.236.0/24 | Valid | RIR databaseARIN | 671 100% |
| 140.235.130.0/24 | Valid | RIR databaseARIN | 671 100% |
| 193.5.251.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.113.99.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 212.113.104.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 216.162.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 77.90.158.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.90.183.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a0d:d940:9006::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0d:d940:900e::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS213529: AS213529:AS-SCULKLTD. 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 (AS213529 isn't in the set, or no route object for AS213529 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 | AS213529 in it | Not covered |
|---|---|---|---|---|---|
| AS213529:AS-SCULKLTD | RIPE | 4 | 1 | Yes | 2 |
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 5 are in fix.csv.
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 147.45.216.0/24 | No route object for it. Add a route object with origin AS213529 in the RIR database for the space. |
| Route object: none | 2a0d:d940:20::/44 | No route object for it. Add a route object with origin AS213529 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213529 whose prefix no peer sees AS213529 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.94.45.0/24 | RIPE | Valid |
| 2a0d:d940:2008::/48 | RIPE | Valid |
| 2a0d:d940:90ab::/48 | 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.