bgpreport

Network · data from 2026-11-12

AS50572 Nordlo Group

Registry name: ZETUPNET Nordlo Improve AB, SE · PeeringDB

15IPv4 routes 93.3% RPKI valid · 100.0% with a route object
3IPv6 routes 66.7% 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
3Route objects not announced registered with origin AS50572, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50572, 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.
192.71.92.0/24 No ROA RIR databaseRIPE 668 99% 67
2001:67c:f68::/48 No ROA RIR databaseRIPE 634 100% 67
37.49.240.0/20 Valid RIR databaseRIPE 670 100% 67
109.205.216.0/21 Valid RIR databaseRIPE 670 100% 67
91.211.168.0/24 Valid RIR databaseRIPE 668 99% 67
91.211.169.0/24 Valid RIR databaseRIPE 668 99% 67
91.211.170.0/23 Valid RIR databaseRIPE 668 99% 67
91.223.47.0/24 Valid RIR databaseRIPE 668 99% 67
91.238.51.0/24 Valid RIR databaseRIPE 668 99% 67
185.5.20.0/22 Valid RIR databaseRIPE 668 99% 67
192.36.222.0/23 Valid RIR databaseRIPE 668 99% 67
193.19.146.0/24 Valid RIR databaseRIPE 668 99% 67
194.0.217.0/24 Valid RIR databaseRIPE 668 99% 67
194.14.104.0/24 Valid RIR databaseRIPE 668 99% 67
194.68.229.0/24 Valid RIR databaseRIPE 668 99% 67
194.103.228.0/22 Valid RIR databaseRIPE 668 99% 67
2a02:1380::/32 Valid RIR databaseRIPE 634 100% 67
2a02:1381::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS50572: AS-ZETUP. 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 (AS50572 isn't in the set, or no route object for AS50572 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 objectsAS50572 in itNot covered
AS-ZETUP RIPE 7150 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 5 are in fix.csv.

  • ROA: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none192.71.92.0/24No ROA covers it. Add a ROA for AS50572, maxLength 24.668 of 673
ROA: none2001:67c:f68::/48No ROA covers it. Add a ROA for AS50572, maxLength 48.634 of 636

Route objects not announced

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

91.211.168.0/22RIPENo ROA
194.103.228.0/24RIPEInvalid: maxLength
2001:67c:2530::/48RIPEValid

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.