bgpreport

Network · data from 2026-11-12

AS203177 PINNACA New Era Technology UK LTD

Registry name: PINNACA New Era Technology UK LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203177, 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.
38.117.73.0/24 No ROA RIR databaseARIN 672 100% 67
91.244.117.0/24 Valid RIR databaseRIPE 673 100% 67
185.135.208.0/24 Valid RIR databaseRIPE 673 100% 67
185.135.209.0/24 Valid RIR databaseRIPE 673 100% 67
185.135.210.0/24 Valid RIR databaseRIPE 673 100% 67
185.135.211.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS203177 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 5 are in fix.csv.

  • ROA: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none38.117.73.0/24No ROA covers it. Add a ROA for AS203177, maxLength 24.672 of 673

Route objects not announced

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

66.129.176.0/20ARINValid
67.226.192.0/20ARINValid
185.135.208.0/22RIPEValid
2a0a:6600::/29RIPEValid

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.