bgpreport

Network · data from 2026-11-12

AS62183 N C in Scandinavia AB

Registry name: NORDICOM Bredband2 Bredbandsson AB, SE · PeeringDB

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

Announced routes

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

77.107.0.0/18 No ROA RIR databaseRIPE 672 100% 67
84.243.0.0/18 No ROA RIR databaseRIPE 672 100% 67
185.32.196.0/22 No ROA RIR databaseRIPE 670 100% 67
185.44.184.0/22 No ROA RIR databaseRIPE 670 100% 67
185.45.84.0/22 No ROA RIR databaseRIPE 670 100% 67
185.105.60.0/22 No ROA RIR databaseRIPE 670 100% 67
185.113.176.0/22 No ROA RIR databaseRIPE 670 100% 67
185.161.212.0/22 No ROA RIR databaseRIPE 670 100% 67
2a02:160::/32 No ROA RIR databaseRIPE 636 100% 67
2a04:57c0::/29 No ROA RIR databaseRIPE 635 100% 67
2a04:9e00::/29 No ROA RIR databaseRIPE 635 100% 67
2a04:a100::/29 No ROA RIR databaseRIPE 635 100% 67
2a06:3580::/29 No ROA RIR databaseRIPE 635 100% 67
2a07:c840::/29 No ROA RIR databaseRIPE 635 100% 67
2a0b:b900::/29 No ROA RIR databaseRIPE 5 1%low visibility 3
185.174.244.0/22 No ROA RIR databaseRIPE 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS62183: AS-NORDICCOM. 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 (AS62183 isn't in the set, or no route object for AS62183 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 objectsAS62183 in itNot covered
AS-NORDICCOM RIPE 4127 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 16 are in fix.csv.

  • ROA: none16
ChangePrefix or setDetailFull-table peers
ROA: none77.107.0.0/18No ROA covers it. Add a ROA for AS62183, maxLength 18.672 of 673
ROA: none84.243.0.0/18No ROA covers it. Add a ROA for AS62183, maxLength 18.672 of 673
ROA: none185.32.196.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.670 of 673
ROA: none185.44.184.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.670 of 673
ROA: none185.45.84.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.670 of 673
ROA: none185.105.60.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.670 of 673
ROA: none185.113.176.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.670 of 673
ROA: none185.161.212.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.670 of 673
ROA: none2a02:160::/32No ROA covers it. Add a ROA for AS62183, maxLength 32.636 of 636
ROA: none2a04:57c0::/29No ROA covers it. Add a ROA for AS62183, maxLength 29.635 of 636
ROA: none2a04:9e00::/29No ROA covers it. Add a ROA for AS62183, maxLength 29.635 of 636
ROA: none2a04:a100::/29No ROA covers it. Add a ROA for AS62183, maxLength 29.635 of 636
ROA: none2a06:3580::/29No ROA covers it. Add a ROA for AS62183, maxLength 29.635 of 636
ROA: none2a07:c840::/29No ROA covers it. Add a ROA for AS62183, maxLength 29.635 of 636
ROA: none2a0b:b900::/29No ROA covers it. Add a ROA for AS62183, maxLength 29.5 of 636
ROA: none185.174.244.0/22No ROA covers it. Add a ROA for AS62183, maxLength 22.3 of 673

Route objects not announced

Every route object with origin AS62183 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.