bgpreport

Network · data from 2026-11-12

AS208626 Serv-Tech

Registry name: serv-tech ServTech LTD, RU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208626, 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.
2a0d:3043:4ffa::/48 No ROA None 456 72% 66
92.119.230.0/24 No ROA RIR databaseRIPE 673 100% 67
176.118.166.0/24 No ROA RIR databaseRIPE 673 100% 67
87.247.142.0/24 No ROA RIR databaseRIPE 671 100% 68
193.47.33.0/24 No ROA RIR databaseRIPE 671 100% 68
193.135.134.0/24 No ROA RIR databaseRIPE 671 100% 68
193.232.179.0/24 No ROA RIR databaseRIPE 671 100% 68
194.93.0.0/24 No ROA RIR databaseRIPE 671 100% 68
194.190.70.0/24 No ROA RIR databaseRIPE 671 100% 68
2a0c:dd80:1001::/48 No ROA RIR databaseRIPE 636 100% 69
2a11:cd03::/32 No ROA RIR databaseRIPE 636 100% 69
2a0f:4305::/32 No ROA RIR databaseRIPE 635 100% 67
2a11:8442::/32 No ROA RIR databaseRIPE 633 100% 67
2a11:b781::/32 No ROA RIR databaseRIPE 633 100% 67
2a12:1547::/32 No ROA RIR databaseRIPE 633 100% 67
95.181.170.0/24 Valid RIR databaseRIPE 673 100% 67
45.89.69.0/24 Valid RIR databaseRIPE 672 100% 67
91.188.222.0/24 Valid RIR databaseRIPE 671 100% 68
95.181.164.0/24 Valid RIR databaseRIPE 671 100% 68
170.168.18.0/24 Valid RIR databaseRIPE 671 100% 68
178.171.122.0/24 Valid RIR databaseRIPE 671 100% 68
185.64.76.0/24 Valid RIR databaseRIPE 671 100% 68
185.170.10.0/24 Valid RIR databaseRIPE 671 100% 68
94.156.2.0/24 Valid RIR databaseRIPE 643 96% 68
2a0c:dd80:1000::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS208626'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 17 are in fix.csv.

  • ROA: none15
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2a0d:3043:4ffa::/48No ROA covers it. Add a ROA for AS208626, maxLength 48.456 of 636
Route object: none2a0d:3043:4ffa::/48No route object for it. Add a route object with origin AS208626 in the RIR database for the space.456 of 636
ROA: none92.119.230.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.673 of 673
ROA: none176.118.166.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.673 of 673
ROA: none87.247.142.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.671 of 673
ROA: none193.47.33.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.671 of 673
ROA: none193.135.134.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.671 of 673
ROA: none193.232.179.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.671 of 673
ROA: none194.93.0.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.671 of 673
ROA: none194.190.70.0/24No ROA covers it. Add a ROA for AS208626, maxLength 24.671 of 673
ROA: none2a0c:dd80:1001::/48No ROA covers it. Add a ROA for AS208626, maxLength 48.636 of 636
ROA: none2a11:cd03::/32No ROA covers it. Add a ROA for AS208626, maxLength 32.636 of 636
ROA: none2a0f:4305::/32No ROA covers it. Add a ROA for AS208626, maxLength 32.635 of 636
ROA: none2a11:8442::/32No ROA covers it. Add a ROA for AS208626, maxLength 32.633 of 636
ROA: none2a11:b781::/32No ROA covers it. Add a ROA for AS208626, maxLength 32.633 of 636
ROA: none2a12:1547::/32No ROA covers it. Add a ROA for AS208626, maxLength 32.633 of 636

Route objects not announced

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

45.155.164.0/24RIPEValid

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.