bgpreport

Network · data from 2026-11-12

AS16175 Signal Bredb�nd

Registry name: Signal Signal Bredband AS, NO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS16175, 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.
2a00:e08::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS16175'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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

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

44.141.140.0/22RIPE-NONAUTHNo ROA
77.110.192.0/18RIPEInvalid: origin
77.222.208.0/22RIPEInvalid: origin
77.222.212.0/23RIPEInvalid: origin
77.222.214.0/23RIPEInvalid: origin
77.222.216.0/21RIPEInvalid: origin
80.89.32.0/19RIPEInvalid: origin
82.148.128.0/19RIPEInvalid: origin
141.0.224.0/19RIPEInvalid: origin
178.16.64.0/20RIPEInvalid: origin
185.10.28.0/22RIPEInvalid: origin
185.130.68.0/22RIPENo ROA
2a00:5d40::/32RIPENo 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.