bgpreport

Network · data from 2026-11-12

AS199954 Techwareca Techwareca Ltd.

Registry name: Techwareca Techwareca Ltd., GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199954, 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.
149.154.176.0/21 No ROA RIR databaseRIPE 672 100% 66
2a13:a300::/29 No ROA RIR databaseRIPE 632 99% 67

AS-SET

AS199954 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 3 are in fix.csv.

  • ROA: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none149.154.176.0/21No ROA covers it. Add a ROA for AS199954, maxLength 21.672 of 673
ROA: none2a13:a300::/29No ROA covers it. Add a ROA for AS199954, maxLength 29.632 of 636

Route objects not announced

Route objects with origin AS199954 whose prefix no peer sees AS199954 announce. Many are kept on purpose (backup routes, space announced only in some places).

149.154.176.0/23RIPENo ROA

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.