Network · data from 2026-11-12

AS200976 Lifestream

Registry name: Lifestream-AS Lifestream Ltd, RU · PeeringDB

5IPv4 routes 40.0% RPKI valid · 60.0% with a route object

0IPv6 routes

2RPKI invalid 0 origin · 2 maxLength

1No ROA 2 with no route object for this origin

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

0Route objects not announced registered with origin AS200976, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS200976, 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.198.112.209/32	Invalid: maxLength	Nonecovered by 185.198.112.0/24	4 1%low visibility	7
185.198.112.213/32	Invalid: maxLength	Nonecovered by 185.198.112.0/24	2 0%low visibility	1
37.18.127.0/24	No ROA	RIR databaseRIPE	673 100%	66
185.198.112.0/24	Valid	RIR databaseRIPE	673 100%	66
185.198.114.0/24	Valid	RIR databaseRIPE	3 0%low visibility	3

185.198.112.209/32

Invalid: maxLength

Nonecovered by 185.198.112.0/24

4 1%low visibility

185.198.112.213/32

Invalid: maxLength

Nonecovered by 185.198.112.0/24

2 0%low visibility

37.18.127.0/24

No ROA

RIR databaseRIPE

673 100%

185.198.112.0/24

Valid

RIR databaseRIPE

673 100%

185.198.114.0/24

Valid

RIR databaseRIPE

3 0%low visibility

AS-SET

AS200976's PeeringDB record names no 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.

ROA: maxLength2
ROA: none1
Route object: none2

Change	Prefix or set	Detail	Full-table peers
ROA: maxLength	185.198.112.209/32	ROA 185.198.112.0/24 AS200976 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.198.112.209/32.	4 of 673
Route object: none	185.198.112.209/32	No route object for it. A route object for 185.198.112.0/24 with origin AS200976 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS200976 in the RIR database for the space.	4 of 673
ROA: maxLength	185.198.112.213/32	ROA 185.198.112.0/24 AS200976 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.198.112.213/32.	2 of 673
Route object: none	185.198.112.213/32	No route object for it. A route object for 185.198.112.0/24 with origin AS200976 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS200976 in the RIR database for the space.	2 of 673
ROA: none	37.18.127.0/24	No ROA covers it. Add a ROA for AS200976, maxLength 24.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: maxLength

185.198.112.209/32

ROA 185.198.112.0/24 AS200976 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.198.112.209/32.

4 of 673

Route object: none

185.198.112.209/32

No route object for it. A route object for 185.198.112.0/24 with origin AS200976 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS200976 in the RIR database for the space.

4 of 673

ROA: maxLength

185.198.112.213/32

ROA 185.198.112.0/24 AS200976 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.198.112.213/32.

2 of 673

Route object: none

185.198.112.213/32

2 of 673

ROA: none

37.18.127.0/24

No ROA covers it. Add a ROA for AS200976, maxLength 24.

673 of 673

Route objects not announced

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