bgpreport

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

1IPv4 routes 100.0% RPKI valid · 0.0% with a route object
1IPv6 routes 100.0% RPKI valid · 0.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
36Route objects not announced registered with origin AS212705, seen from no peer

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% 67
2a0e:e00::/29 Valid None 635 100% 67

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
ChangePrefix or setDetailFull-table peers
Route object: none217.138.29.0/24No route object for it. Add a route object with origin AS212705 in the RIR database for the space.673 of 673
Route object: none2a0e:e00::/29No route object for it. Add a route object with origin AS212705 in the RIR database for the space.635 of 636

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/23APNICValid
103.157.110.0/24APNICValid
103.157.111.0/24APNICValid
2406:9dc0:70::/44APNICValid
2406:9dc0:70::/45APNICValid
2406:9dc0:70::/46APNICValid
2406:9dc0:70::/47APNICValid
2406:9dc0:70::/48APNICValid
2406:9dc0:71::/48APNICValid
2406:9dc0:72::/47APNICValid
2406:9dc0:72::/48APNICValid
2406:9dc0:73::/48APNICValid
2406:9dc0:74::/46APNICValid
2406:9dc0:74::/47APNICValid
2406:9dc0:74::/48APNICValid
2406:9dc0:75::/48APNICValid
2406:9dc0:76::/47APNICValid
2406:9dc0:76::/48APNICValid
2406:9dc0:77::/48APNICValid
2406:9dc0:78::/45APNICValid
2406:9dc0:78::/46APNICValid
2406:9dc0:78::/47APNICValid
2406:9dc0:78::/48APNICValid
2406:9dc0:79::/48APNICValid
2406:9dc0:7a::/47APNICValid
2406:9dc0:7a::/48APNICValid
2406:9dc0:7b::/48APNICValid
2406:9dc0:7c::/46APNICValid
2406:9dc0:7c::/47APNICValid
2406:9dc0:7c::/48APNICValid
2406:9dc0:7d::/48APNICValid
2406:9dc0:7e::/47APNICValid
2406:9dc0:7e::/48APNICValid
2406:9dc0:7f::/48APNICValid
2602:feda:b70::/48ARINValid
2602:feda:b71::/48ARINValid

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.