bgpreport

Network · data from 2026-11-12

AS215336 HOVEDKVARTERETIT Hovedkvarteret IT AS

Registry name: HOVEDKVARTERETIT Hovedkvarteret IT AS, NO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215336, 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.
37.202.57.192/26 Invalid: origin None 1 0%low visibility 1
176.125.233.240/28 Invalid: origin None 1 0%low visibility 1
176.125.235.0/28 Invalid: origin None 1 0%low visibility 1
185.35.203.0/24 Valid RIR databaseRIPE 672 100% 67
37.202.56.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: origin3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: origin37.202.57.192/26ROAs covering it name AS50304, not AS215336. If AS215336 should announce it, add a ROA for AS215336.1 of 673
Route object: none37.202.57.192/26No route object for it. Add a route object with origin AS215336 in the RIR database for the space.1 of 673
ROA: origin176.125.233.240/28ROAs covering it name AS50304, not AS215336. If AS215336 should announce it, add a ROA for AS215336.1 of 673
Route object: none176.125.233.240/28No route object for it. Add a route object with origin AS215336 in the RIR database for the space.1 of 673
ROA: origin176.125.235.0/28ROAs covering it name AS50304, not AS215336. If AS215336 should announce it, add a ROA for AS215336.1 of 673
Route object: none176.125.235.0/28No route object for it. Add a route object with origin AS215336 in the RIR database for the space.1 of 673

Route objects not announced

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