bgpreport

Network · data from 2026-11-12

AS44112 SWEB-AS SpaceWeb Ltd

Registry name: SWEB-AS SpaceWeb Ltd, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS44112, 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.
194.226.98.0/23 No ROA RIR databaseRIPE 673 100% 67
195.208.21.0/24 No ROA RIR databaseRIPE 673 100% 67
195.208.60.0/23 No ROA RIR databaseRIPE 673 100% 67
195.208.120.0/21 No ROA RIR databaseRIPE 673 100% 67
195.208.120.0/22 No ROA RIR databaseRIPE 673 100% 67
195.208.124.0/22 No ROA RIR databaseRIPE 673 100% 67
193.232.88.0/22 No ROA RIR databaseRIPE 670 100% 67
195.208.20.0/24 No ROA RIR databaseRIPE 669 99% 67
77.222.49.0/24 Valid Nonecovered by 77.222.48.0/23 672 100% 67
77.222.36.0/24 Valid Nonecovered by 77.222.36.0/23 667 99% 67
31.177.82.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.32.0/24 Valid RIR databaseRIPE 673 100% 67
77.222.35.0/24 Valid RIR databaseRIPE 673 100% 67
77.222.36.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.38.0/24 Valid RIR databaseRIPE 673 100% 67
77.222.40.0/22 Valid RIR databaseRIPE 673 100% 67
77.222.42.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.48.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.50.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.52.0/22 Valid RIR databaseRIPE 673 100% 67
77.222.52.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.54.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.56.0/22 Valid RIR databaseRIPE 673 100% 67
77.222.56.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.58.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.60.0/22 Valid RIR databaseRIPE 673 100% 67
77.222.60.0/23 Valid RIR databaseRIPE 673 100% 67
80.93.52.0/24 Valid RIR databaseRIPE 673 100% 67
80.93.60.0/22 Valid RIR databaseRIPE 673 100% 67
168.222.140.0/23 Valid RIR databaseRIPE 673 100% 67
168.222.202.0/23 Valid RIR databaseRIPE 673 100% 67
77.222.40.0/23 Valid RIR databaseRIPE 672 100% 67
77.222.46.0/23 Valid RIR databaseRIPE 672 100% 67
77.222.62.0/23 Valid RIR databaseRIPE 670 100% 67
77.222.39.0/24 Valid RIR databaseRIPE 668 99% 67
77.222.44.0/24 Valid RIR databaseRIPE 668 99% 67
2a02:408:7722::/48 Valid RIR databaseRIPE 636 100% 69

AS-SET

AS44112 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none194.226.98.0/23No ROA covers it. Add a ROA for AS44112, maxLength 23.673 of 673
ROA: none195.208.21.0/24No ROA covers it. Add a ROA for AS44112, maxLength 24.673 of 673
ROA: none195.208.60.0/23No ROA covers it. Add a ROA for AS44112, maxLength 23.673 of 673
ROA: none195.208.120.0/21No ROA covers it. Add a ROA for AS44112, maxLength 21.673 of 673
ROA: none195.208.120.0/22No ROA covers it. Add a ROA for AS44112, maxLength 22.673 of 673
ROA: none195.208.124.0/22No ROA covers it. Add a ROA for AS44112, maxLength 22.673 of 673
ROA: none193.232.88.0/22No ROA covers it. Add a ROA for AS44112, maxLength 22.670 of 673
ROA: none195.208.20.0/24No ROA covers it. Add a ROA for AS44112, maxLength 24.669 of 673
Route object: none77.222.49.0/24No route object for it. A route object for 77.222.48.0/23 with origin AS44112 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44112 in the RIR database for the space.672 of 673
Route object: none77.222.36.0/24No route object for it. A route object for 77.222.36.0/23 with origin AS44112 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44112 in the RIR database for the space.667 of 673

Route objects not announced

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

77.222.36.0/22RIPEValid
77.222.50.0/24RIPEValid
77.222.51.0/24RIPEValid
77.222.63.0/24RIPEValid
130.117.204.0/24RADBNo ROA
195.208.20.0/23RIPENo 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.