bgpreport

Network · data from 2026-11-12

AS44393 SBRC Securebit AG

Registry name: SBRC Securebit AG, CH · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44393, 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.
172.31.1.1/32 bogon No ROA None 1 0%low visibility 1
::/0 bogon No ROA None 1 0%low visibility 1

AS-SET

AS44393 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 2 are in fix.csv.

  • Bogon prefix2
ChangePrefix or setDetailFull-table peers
Bogon prefix172.31.1.1/32In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
Bogon prefix::/0In IANA's special-purpose registry: default route.1 of 636

Route objects not announced

Every route object with origin AS44393 is announced.

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.