Network · data from 2026-11-12
AS64089 DNSFILTER-AS-AP - DNSFilter, Inc.
Registry name: DNSFILTER-AS-AP - DNSFilter, Inc., AU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS64089, 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.
| 2402:5c40:2000::/48 | No ROA | Other IRR onlyRADB | 344 54% |
| 45.54.28.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2607:f740:e005::/48 | Valid | Other IRR onlyRADB | 634 100% |
| 103.85.42.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.247.36.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 103.247.37.0/24 | Valid | RIR databaseAPNIC, RADB | 672 100% |
| 45.253.131.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 103.85.43.0/24 | Valid | RIR databaseAPNIC, RADB | 671 100% |
| 2402:5c40:5c40::/48 | Valid | RIR databaseAPNIC, RADB | 634 100% |
| 2402:5c40:5c42::/48 | Valid | RIR databaseAPNIC, RADB | 634 100% |
| 2402:5c40:5c41::/48 | Valid | RIR databaseAPNIC | 633 100% |
| 2402:5c40:5c43::/48 | Valid | RIR databaseAPNIC | 633 100% |
AS-SET
AS64089 isn't in PeeringDB, where networks name their 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 19 are in fix.csv.
- ROA: none1
- Route object: RIR3
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2402:5c40:2000::/48 | No ROA covers it. Add a ROA for AS64089, maxLength 48. |
| Route object: RIR | 2402:5c40:2000::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.54.28.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2607:f740:e005::/48 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS64089 whose prefix no peer sees AS64089 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.54.84.0/24 | RADB | Valid |
| 45.54.85.0/24 | RADB | Valid |
| 45.253.130.0/23 | APNIC | Valid |
| 45.253.130.0/24 | APNIC | Valid |
| 67.158.62.0/24 | RADB | Valid |
| 103.85.42.0/23 | APNIC | Valid |
| 103.247.36.0/23 | APNIC, RADB | Valid |
| 148.59.115.0/24 | RADB | Valid |
| 2402:5c40:1000::/40 | APNIC | Valid |
| 2402:5c40:1100::/40 | APNIC | Valid |
| 2402:5c40:1200::/40 | APNIC | Valid |
| 2402:5c40:1300::/40 | APNIC | Valid |
| 2402:5c40:1400::/40 | APNIC | Valid |
| 2402:5c40:1500::/40 | APNIC | Valid |
| 2402:5c40:5c00::/40 | 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.