Network · data from 2026-11-12
AS212705 TIG-Network TIG Management Services Limited
Registry name: TIG-Network TIG Management Services Limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212705, 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.
| 217.138.29.0/24 | Valid | None | 673 100% |
| 2a0e:e00::/29 | Valid | None | 635 100% |
AS-SET
AS212705 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 38 are in fix.csv.
- Route object: none2
- Route object: not announced36
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 217.138.29.0/24 | No route object for it. Add a route object with origin AS212705 in the RIR database for the space. |
| Route object: none | 2a0e:e00::/29 | No route object for it. Add a route object with origin AS212705 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS212705 whose prefix no peer sees AS212705 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.157.110.0/23 | APNIC | Valid |
| 103.157.110.0/24 | APNIC | Valid |
| 103.157.111.0/24 | APNIC | Valid |
| 2406:9dc0:70::/44 | APNIC | Valid |
| 2406:9dc0:70::/45 | APNIC | Valid |
| 2406:9dc0:70::/46 | APNIC | Valid |
| 2406:9dc0:70::/47 | APNIC | Valid |
| 2406:9dc0:70::/48 | APNIC | Valid |
| 2406:9dc0:71::/48 | APNIC | Valid |
| 2406:9dc0:72::/47 | APNIC | Valid |
| 2406:9dc0:72::/48 | APNIC | Valid |
| 2406:9dc0:73::/48 | APNIC | Valid |
| 2406:9dc0:74::/46 | APNIC | Valid |
| 2406:9dc0:74::/47 | APNIC | Valid |
| 2406:9dc0:74::/48 | APNIC | Valid |
| 2406:9dc0:75::/48 | APNIC | Valid |
| 2406:9dc0:76::/47 | APNIC | Valid |
| 2406:9dc0:76::/48 | APNIC | Valid |
| 2406:9dc0:77::/48 | APNIC | Valid |
| 2406:9dc0:78::/45 | APNIC | Valid |
| 2406:9dc0:78::/46 | APNIC | Valid |
| 2406:9dc0:78::/47 | APNIC | Valid |
| 2406:9dc0:78::/48 | APNIC | Valid |
| 2406:9dc0:79::/48 | APNIC | Valid |
| 2406:9dc0:7a::/47 | APNIC | Valid |
| 2406:9dc0:7a::/48 | APNIC | Valid |
| 2406:9dc0:7b::/48 | APNIC | Valid |
| 2406:9dc0:7c::/46 | APNIC | Valid |
| 2406:9dc0:7c::/47 | APNIC | Valid |
| 2406:9dc0:7c::/48 | APNIC | Valid |
| 2406:9dc0:7d::/48 | APNIC | Valid |
| 2406:9dc0:7e::/47 | APNIC | Valid |
| 2406:9dc0:7e::/48 | APNIC | Valid |
| 2406:9dc0:7f::/48 | APNIC | Valid |
| 2602:feda:b70::/48 | ARIN | Valid |
| 2602:feda:b71::/48 | ARIN | 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.