bgpreport

Network · data from 2026-11-12

AS49515 Nordiska Servercentralen

Registry name: DNDSWEDEN DND Nordic AB, SE · PeeringDB

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

Announced routes

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

212.91.144.0/22 No ROA None 672 100% 67
104.160.12.0/24 No ROA RIR databaseRIPE 672 100% 66
104.160.13.0/24 No ROA RIR databaseRIPE 672 100% 66
185.230.32.0/22 Valid RIR databaseRIPE 673 100% 66
188.95.32.0/21 Valid RIR databaseRIPE 673 100% 66
194.68.231.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS49515: AS-NSC. 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 (AS49515 isn't in the set, or no route object for AS49515 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 objectsAS49515 in itNot covered
AS-NSC RIPE 217 Yes 1

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: none3
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none212.91.144.0/22No ROA covers it. Add a ROA for AS49515, maxLength 22.672 of 673
Route object: none212.91.144.0/22No route object for it. Add a route object with origin AS49515 in the RIR database for the space.672 of 673
ROA: none104.160.12.0/24No ROA covers it. Add a ROA for AS49515, maxLength 24.672 of 673
ROA: none104.160.13.0/24No ROA covers it. Add a ROA for AS49515, maxLength 24.672 of 673

Route objects not announced

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

2a02:ca80::/29RIPENo 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.