bgpreport

Network · data from 2026-11-12

AS56361 ORGTECH-AS Orgtechservice Ltd

Registry name: ORGTECH-AS Orgtechservice Ltd, RU · not in PeeringDB

22IPv4 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
0Route objects not announced registered with origin AS56361, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS56361, 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.
2a02:2808:1009::/48 No ROA RIR databaseRIPE 636 100% 69
31.41.184.0/21 Valid RIR databaseRIPE 673 100% 66
31.148.52.0/22 Valid RIR databaseRIPE 673 100% 66
31.148.104.0/21 Valid RIR databaseRIPE 673 100% 66
31.148.112.0/21 Valid RIR databaseRIPE 673 100% 66
46.175.120.0/21 Valid RIR databaseRIPE 673 100% 66
92.38.56.0/21 Valid RIR databaseRIPE 673 100% 66
92.38.80.0/22 Valid RIR databaseRIPE 673 100% 66
93.170.166.0/23 Valid RIR databaseRIPE 673 100% 66
93.171.34.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.128.0/21 Valid RIR databaseRIPE 673 100% 66
95.46.166.0/23 Valid RIR databaseRIPE 673 100% 66
95.46.216.0/21 Valid RIR databaseRIPE 673 100% 66
146.158.48.0/21 Valid RIR databaseRIPE 673 100% 66
176.98.168.0/21 Valid RIR databaseRIPE 673 100% 66
176.118.128.0/21 Valid RIR databaseRIPE 673 100% 66
31.148.40.0/21 Valid RIR databaseRIPE 672 100% 66
31.148.56.0/21 Valid RIR databaseRIPE 672 100% 66
31.148.192.0/22 Valid RIR databaseRIPE 672 100% 66
93.170.192.0/21 Valid RIR databaseRIPE 672 100% 66
93.171.36.0/22 Valid RIR databaseRIPE 672 100% 66
95.46.168.0/22 Valid RIR databaseRIPE 672 100% 66
95.46.172.0/22 Valid RIR databaseRIPE 672 100% 66

AS-SET

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

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2a02:2808:1009::/48No ROA covers it. Add a ROA for AS56361, maxLength 48.636 of 636

Route objects not announced

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