bgpreport

Network · data from 2026-11-12

AS43770 ITCONNECT-AS ITCONNECT Scandinavia AB

Registry name: ITCONNECT-AS ITCONNECT Scandinavia AB, SE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43770, 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.
82.99.5.0/24 Invalid: origin None 2 0%low visibility 2
2001:67c:19d0::/48 No ROA Other origin only 635 100% 67
91.195.154.0/23 Valid RIR databaseRIPE 672 100% 66
185.153.4.0/22 Valid RIR databaseRIPE 672 100% 66
185.210.220.0/22 Valid RIR databaseRIPE 672 100% 66
2a07:84c0::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin82.99.5.0/24ROAs covering it name AS12552, not AS43770. If AS43770 should announce it, add a ROA for AS43770.2 of 673
Route object: none82.99.5.0/24No route object for it. Add a route object with origin AS43770 in the RIR database for the space.2 of 673
ROA: none2001:67c:19d0::/48No ROA covers it. Add a ROA for AS43770, maxLength 48.635 of 636
Route object: none2001:67c:19d0::/48Route objects for it name AS12552. Add a route object with origin AS43770 in the RIR database for the space.635 of 636

Route objects not announced

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