bgpreport

Network · data from 2026-11-12

AS50343 New Work SE

Registry name: NWRK-AS New Work SE, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50343, 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.

109.233.152.0/24 Valid Nonecovered by 109.233.152.0/22 2 0%low visibility 2
109.233.156.0/22 Valid RIR databaseRIPE 2 0%low visibility 2
185.169.112.0/22 Valid RIR databaseRIPE 2 0%low visibility 2
185.169.112.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS50343: AS-NWRK. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS50343 isn't in the set, or no route object for AS50343 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS50343 in itNot covered
AS-NWRK RIPE 1110 Yes 0

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

  • Route object: none1
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
Route object: none109.233.152.0/24No route object for it. A route object for 109.233.152.0/22 with origin AS50343 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50343 in the RIR database for the space.2 of 673

Route objects not announced

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

109.233.152.0/21RIPEValid
109.233.152.0/22RIPEValid
109.233.156.0/24RIPEValid
185.169.113.0/24RIPEValid
2a01:8780::/29RIPEValid
2a01:8780::/32RIPEValid
2a01:8781::/32RIPEValid

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.