Network · data from 2026-11-12
AS38004 FastLink Wireless ISP
Registry name: FASTLINK-ISP - FastLink Wireless ISP, DrukCom Pvt. Enterprise., BT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38004, 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.
| 2401:5f40::/32 | Valid | None | 1 0%low visibility |
| 202.89.24.0/21 | Valid | RIR databaseAPNIC | 671 100% |
AS-SET
AS38004'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 8 are in fix.csv.
- Route object: none1
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2401:5f40::/32 | No route object for it. Add a route object with origin AS38004 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS38004 whose prefix no peer sees AS38004 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 202.89.24.0/25 | APNIC | Valid |
| 202.89.24.128/25 | APNIC | Valid |
| 202.89.25.0/24 | APNIC | Valid |
| 202.89.25.0/25 | APNIC | Valid |
| 202.89.25.128/25 | APNIC | Valid |
| 202.89.26.0/24 | APNIC | Valid |
| 202.89.29.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.