Network · data from 2026-11-12
AS17551 Swoop Residential
Registry name: ANYCAST-AS-AP - Anycast Global Backbone, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS17551, 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.
| 165.101.148.0/23 | No ROA | Nonecovered by 165.101.148.0/22 | 673 100% |
| 2402:1560::/32 | No ROA | Other IRR onlyRADB | 636 100% |
| 103.240.228.0/22 | No ROA | RIR databaseAPNIC, RADB | 673 100% |
| 125.254.110.0/23 | Valid | Other IRR onlyRADB | 673 100% |
| 103.15.148.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 103.29.172.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.29.173.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.53.117.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.53.118.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.53.119.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.227.64.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.232.252.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 117.53.128.0/20 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 123.50.128.0/20 | Valid | RIR databaseAPNIC | 673 100% |
| 123.50.128.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 123.50.136.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 123.50.140.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 123.50.148.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 125.214.80.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 125.254.104.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 125.254.108.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 125.254.116.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 125.254.118.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 125.254.120.0/21 | Valid | RIR databaseAPNIC | 673 100% |
| 125.254.120.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 125.254.124.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 202.47.120.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 202.169.22.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 203.22.132.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.27.231.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.30.68.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 203.83.4.0/22 | Valid | RIR databaseAPNIC | 673 100% |
| 203.147.96.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 673 100% |
| 14.192.56.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 210.56.224.0/22 | Valid | RIR databaseAPNIC | 672 100% |
| 210.56.228.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 210.56.237.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 210.56.243.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 210.56.254.0/23 | Valid | RIR databaseAPNIC | 672 100% |
| 110.232.240.0/21 | Valid | RIR databaseAPNIC, NTTCOM | 670 100% |
| 2400:b880::/32 | Valid | RIR databaseAPNIC | 636 100% |
| 2407:5400::/32 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
AS17551's PeeringDB record names no AS-SET.
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 23 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: RIR2
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 165.101.148.0/23 | No ROA covers it. Add a ROA for AS17551, maxLength 23. |
| Route object: none | 165.101.148.0/23 | No route object for it. A route object for 165.101.148.0/22 with origin AS17551 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17551 in the RIR database for the space. |
| ROA: none | 2402:1560::/32 | No ROA covers it. Add a ROA for AS17551, maxLength 32. |
| Route object: RIR | 2402:1560::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 103.240.228.0/22 | No ROA covers it. Add a ROA for AS17551, maxLength 22. |
| Route object: RIR | 125.254.110.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS17551 whose prefix no peer sees AS17551 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 14.192.56.0/23 | APNIC | Valid |
| 14.192.58.0/23 | APNIC | Valid |
| 103.17.220.0/22 | RADB | No ROA |
| 103.17.220.0/24 | RADB | No ROA |
| 103.17.221.0/24 | RADB | No ROA |
| 103.17.222.0/24 | RADB | No ROA |
| 103.17.223.0/24 | RADB | No ROA |
| 103.240.228.0/23 | APNIC | No ROA |
| 103.240.228.0/24 | APNIC | No ROA |
| 103.240.229.0/24 | APNIC | No ROA |
| 103.240.230.0/23 | APNIC | No ROA |
| 103.240.230.0/24 | APNIC | No ROA |
| 103.240.231.0/24 | APNIC | No ROA |
| 165.101.148.0/22 | RADB | No ROA |
| 203.56.241.0/24 | RADB | No ROA |
| 203.56.253.0/24 | RADB | No ROA |
| 210.56.241.0/24 | APNIC | 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.