bgpreport

Network · data from 2026-11-12

AS211134 Intersys

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211134, 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.
94.228.206.0/24 Invalid: origin RIR databaseRIPE 137 20% 48
89.23.122.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS211134'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 1 are in fix.csv.

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin94.228.206.0/24ROAs covering it name AS48293, not AS211134. If AS211134 should announce it, add a ROA for AS211134.137 of 673

Route objects not announced

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