Network · data from 2026-11-12

AS51369 FIORD-RU-AS LLC "TRC FIORD"

Registry name: FIORD-RU-AS LLC "TRC FIORD", RU · not in PeeringDB

27IPv4 routes 96.3% RPKI valid · 100.0% with a route object

4IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

1Low visibility seen by under 10% of full-table peers

12Route objects not announced registered with origin AS51369, seen from no peer

Announced routes

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


185.221.44.0/22	No ROA	RIR databaseRIPE	2 0%low visibility	2
46.44.0.0/18	Valid	RIR databaseRIPE	673 100%	66
62.140.224.0/19	Valid	RIR databaseRIPE	673 100%	66
62.140.250.0/24	Valid	RIR databaseRIPE	673 100%	66
80.77.172.0/22	Valid	RIR databaseRIPE	673 100%	66
82.194.244.0/22	Valid	RIR databaseRIPE	673 100%	66
93.191.8.0/21	Valid	RIR databaseRIPE	673 100%	66
93.191.11.0/24	Valid	RIR databaseRIPE	673 100%	66
93.191.12.0/23	Valid	RIR databaseRIPE	673 100%	66
62.204.32.0/24	Valid	RIR databaseRIPE	672 100%	67
80.77.161.0/24	Valid	RIR databaseRIPE	672 100%	67
80.77.162.0/23	Valid	RIR databaseRIPE	672 100%	66
80.77.169.0/24	Valid	RIR databaseRIPE	672 100%	66
80.77.170.0/23	Valid	RIR databaseRIPE	672 100%	66
89.188.167.0/24	Valid	RIR databaseRIPE	672 100%	66
89.188.176.0/22	Valid	RIR databaseRIPE	672 100%	66
91.209.127.0/24	Valid	RIR databaseRIPE	672 100%	67
91.239.132.0/22	Valid	RIR databaseRIPE	672 100%	66
137.22.159.0/24	Valid	RIR databaseRIPE	672 100%	67
168.113.163.0/24	Valid	RIR databaseRIPE	672 100%	67
185.16.116.0/22	Valid	RIR databaseRIPE	672 100%	66
185.221.45.0/24	Valid	RIR databaseRIPE	672 100%	66
185.221.46.0/24	Valid	RIR databaseRIPE	672 100%	66
185.221.47.0/24	Valid	RIR databaseRIPE	672 100%	66
193.176.227.0/24	Valid	RIR databaseRIPE	672 100%	67
194.15.126.0/23	Valid	RIR databaseRIPE	672 100%	66
194.190.2.0/23	Valid	RIR databaseRIPE	672 100%	67
2a02:2518::/32	Valid	RIR databaseRIPE	633 100%	67
2a02:2518::/29	Valid	RIR databaseRIPE	632 99%	67
2001:67c:1484::/48	Valid	RIR databaseRIPE	604 95%	67
2a04:280::/29	Valid	RIR databaseRIPE	603 95%	67

185.221.44.0/22

No ROA

RIR databaseRIPE

2 0%low visibility

46.44.0.0/18

Valid

RIR databaseRIPE

673 100%

62.140.224.0/19

Valid

RIR databaseRIPE

673 100%

62.140.250.0/24

Valid

RIR databaseRIPE

673 100%

80.77.172.0/22

Valid

RIR databaseRIPE

673 100%

82.194.244.0/22

Valid

RIR databaseRIPE

673 100%

93.191.8.0/21

Valid

RIR databaseRIPE

673 100%

93.191.11.0/24

Valid

RIR databaseRIPE

673 100%

93.191.12.0/23

Valid

RIR databaseRIPE

673 100%

62.204.32.0/24

Valid

RIR databaseRIPE

672 100%

80.77.161.0/24

Valid

RIR databaseRIPE

672 100%

80.77.162.0/23

Valid

RIR databaseRIPE

672 100%

80.77.169.0/24

Valid

RIR databaseRIPE

672 100%

80.77.170.0/23

Valid

RIR databaseRIPE

672 100%

89.188.167.0/24

Valid

RIR databaseRIPE

672 100%

89.188.176.0/22

Valid

RIR databaseRIPE

672 100%

91.209.127.0/24

Valid

RIR databaseRIPE

672 100%

91.239.132.0/22

Valid

RIR databaseRIPE

672 100%

137.22.159.0/24

Valid

RIR databaseRIPE

672 100%

168.113.163.0/24

Valid

RIR databaseRIPE

672 100%

185.16.116.0/22

Valid

RIR databaseRIPE

672 100%

185.221.45.0/24

Valid

RIR databaseRIPE

672 100%

185.221.46.0/24

Valid

RIR databaseRIPE

672 100%

185.221.47.0/24

Valid

RIR databaseRIPE

672 100%

193.176.227.0/24

Valid

RIR databaseRIPE

672 100%

194.15.126.0/23

Valid

RIR databaseRIPE

672 100%

194.190.2.0/23

Valid

RIR databaseRIPE

672 100%

2a02:2518::/32

Valid

RIR databaseRIPE

633 100%

2a02:2518::/29

Valid

RIR databaseRIPE

632 99%

2001:67c:1484::/48

Valid

RIR databaseRIPE

604 95%

2a04:280::/29

Valid

RIR databaseRIPE

603 95%

AS-SET

AS51369 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 13 are in fix.csv.

ROA: none1
Route object: not announced12

Change	Prefix or set	Detail	Full-table peers
ROA: none	185.221.44.0/22	No ROA covers it. Add a ROA for AS51369, maxLength 22.	2 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

185.221.44.0/22

No ROA covers it. Add a ROA for AS51369, maxLength 22.

2 of 673

Route objects not announced

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


62.140.228.0/23	RIPE	Valid
62.140.231.0/24	RIPE	Valid
62.140.232.0/24	RIPE	Valid
62.140.233.0/24	RIPE	Valid
62.140.234.0/23	RIPE	Valid
62.140.240.0/23	RIPE	Valid
62.140.242.0/24	RIPE	Valid
62.140.248.0/24	RIPE	Valid
62.140.249.0/24	RIPE	Valid
62.140.251.0/24	RIPE	Valid
62.140.252.0/23	RIPE	Valid
93.191.14.0/24	RIPE	Valid

62.140.228.0/23

RIPE

Valid

62.140.231.0/24

RIPE

Valid

62.140.232.0/24

RIPE

Valid

62.140.233.0/24

RIPE

Valid

62.140.234.0/23

RIPE

Valid

62.140.240.0/23

RIPE

Valid

62.140.242.0/24

RIPE

Valid

62.140.248.0/24

RIPE

Valid

62.140.249.0/24

RIPE

Valid

62.140.251.0/24

RIPE

Valid

62.140.252.0/23

RIPE

Valid

93.191.14.0/24

RIPE

Valid

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.