Network · data from 2026-11-12

AS212286 LONCONNECT LonConnect Ltd

Registry name: LONCONNECT LonConnect Ltd, GB · not in PeeringDB

26IPv4 routes 100.0% RPKI valid · 100.0% with a route object

1IPv6 routes 0.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

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

5Route objects not announced registered with origin AS212286, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS212286, 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:fc80::/29	No ROA	RIR databaseRIPE	634 100%	67
45.87.128.0/23	Valid	RIR databaseRIPE	673 100%	67
45.128.80.0/22	Valid	RIR databaseRIPE	673 100%	67
45.131.216.0/22	Valid	RIR databaseRIPE	673 100%	67
45.132.164.0/22	Valid	RIR databaseRIPE	673 100%	67
45.138.248.0/22	Valid	RIR databaseRIPE	673 100%	67
45.145.136.0/22	Valid	RIR databaseRIPE	673 100%	67
45.153.36.0/22	Valid	RIR databaseRIPE	673 100%	67
45.154.148.0/22	Valid	RIR databaseRIPE	673 100%	67
81.85.32.0/20	Valid	RIR databaseRIPE	673 100%	67
136.148.144.0/22	Valid	RIR databaseRIPE	673 100%	67
152.114.202.0/23	Valid	RIR databaseRIPE	673 100%	67
152.114.204.0/23	Valid	RIR databaseRIPE	673 100%	67
158.94.188.0/22	Valid	RIR databaseRIPE	673 100%	67
158.94.217.0/24	Valid	RIR databaseRIPE	673 100%	67
185.121.236.0/22	Valid	RIR databaseRIPE	673 100%	67
193.17.224.0/24	Valid	RIR databaseRIPE	673 100%	67
193.17.231.0/24	Valid	RIR databaseRIPE	673 100%	67
193.17.253.0/24	Valid	RIR databaseRIPE	673 100%	67
193.17.255.0/24	Valid	RIR databaseRIPE	673 100%	67
212.97.80.0/21	Valid	RIR databaseRIPE	673 100%	67
212.102.124.0/24	Valid	RIR databaseRIPE	673 100%	67
213.184.68.0/22	Valid	RIR databaseRIPE	673 100%	67
217.179.80.0/22	Valid	RIR databaseRIPE	673 100%	67
217.180.44.0/22	Valid	RIR databaseRIPE	673 100%	67
45.91.73.0/24	Valid	RIR databaseRIPE	672 100%	67
45.129.72.0/24	Valid	RIR databaseRIPE	672 100%	66

AS-SET

AS212286 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: none1
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a0e:fc80::/29	No ROA covers it. Add a ROA for AS212286, maxLength 29.	634 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a0e:fc80::/29

No ROA covers it. Add a ROA for AS212286, maxLength 29.

634 of 636

Route objects not announced

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


45.131.218.0/23	RIPE	Invalid: maxLength
45.138.250.0/23	RIPE	Invalid: maxLength
45.145.138.0/23	RIPE	Invalid: maxLength
45.154.150.0/23	RIPE	Invalid: maxLength
2a0e:fc87:fffe::/47	RIPE	No ROA

45.131.218.0/23

RIPE

Invalid: maxLength

45.138.250.0/23

RIPE

Invalid: maxLength

45.145.138.0/23

RIPE

Invalid: maxLength

45.154.150.0/23

RIPE

Invalid: maxLength

2a0e:fc87:fffe::/47

RIPE

No ROA

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.