bgpreport

Network · data from 2026-11-12

AS47454 SXTNORTH 60 North ApS

Registry name: SXTNORTH 60 North ApS, DK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47454, 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.
2a0e:3a80::/32 Valid Other origin only 635 100% 67
45.80.40.0/22 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS47454 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 5 are in fix.csv.

  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2a0e:3a80::/32Route objects for it name AS208741. Add a route object with origin AS47454 in the RIR database for the space.635 of 636

Route objects not announced

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

45.80.40.0/23RIPEInvalid: maxLength
45.80.42.0/24RIPEInvalid: maxLength
45.80.43.0/24RIPEInvalid: maxLength
185.230.197.0/24RIPEInvalid: origin

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.