bgpreport

Network · data from 2026-11-12

AS43362 MAJORDOMO Hosting Ltd

Registry name: MAJORDOMO Hosting Ltd, RU · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43362, 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.

178.250.246.228/32 Invalid: maxLength Nonecovered by 178.250.246.0/23 4 1%low visibility 7
78.108.81.0/24 No ROA RIR databaseRIPE 673 100% 66
78.108.84.0/23 No ROA RIR databaseRIPE 673 100% 66
185.84.110.0/23 No ROA RIR databaseRIPE 673 100% 66
37.153.64.0/23 Valid Nonecovered by 37.153.64.0/22 673 100% 66
37.153.70.0/24 Valid RIR databaseRIPE 673 100% 66
78.108.80.0/24 Valid RIR databaseRIPE 673 100% 66
78.108.82.0/23 Valid RIR databaseRIPE 673 100% 66
78.108.86.0/23 Valid RIR databaseRIPE 673 100% 66
78.108.88.0/23 Valid RIR databaseRIPE 673 100% 66
78.108.90.0/23 Valid RIR databaseRIPE 673 100% 66
78.108.92.0/23 Valid RIR databaseRIPE 673 100% 66
78.108.94.0/23 Valid RIR databaseRIPE 673 100% 66
130.49.174.0/24 Valid RIR databaseRIPE 673 100% 66
178.250.241.0/24 Valid RIR databaseRIPE 673 100% 66
178.250.242.0/23 Valid RIR databaseRIPE 673 100% 66
178.250.244.0/23 Valid RIR databaseRIPE 673 100% 66
178.250.246.0/23 Valid RIR databaseRIPE 673 100% 66
185.84.108.0/23 Valid RIR databaseRIPE 673 100% 66
178.250.240.0/23 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

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

  • ROA: maxLength1
  • ROA: none3
  • Route object: none2
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: maxLength178.250.246.228/32ROA 178.250.240.0/21 AS43362 has maxLength 24; ROA 178.250.246.0/23 AS43362 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 178.250.246.228/32.4 of 673
Route object: none178.250.246.228/32No route object for it. A route object for 178.250.246.0/23 with origin AS43362 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43362 in the RIR database for the space.4 of 673
ROA: none78.108.81.0/24No ROA covers it. Add a ROA for AS43362, maxLength 24.673 of 673
ROA: none78.108.84.0/23No ROA covers it. Add a ROA for AS43362, maxLength 23.673 of 673
ROA: none185.84.110.0/23No ROA covers it. Add a ROA for AS43362, maxLength 23.673 of 673
Route object: none37.153.64.0/23No route object for it. A route object for 37.153.64.0/22 with origin AS43362 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43362 in the RIR database for the space.673 of 673

Route objects not announced

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

37.153.64.0/22RIPEValid
37.153.68.0/23RIPEValid
78.108.86.0/24RIPEInvalid: maxLength
78.108.87.0/24RIPEInvalid: maxLength
78.108.88.0/21RIPENo ROA
178.250.240.0/22RIPEValid
178.250.240.0/24RIPEValid
178.250.244.0/22RIPEValid
178.250.244.0/24RIPEValid
178.250.245.0/24RIPEValid
2a02:dac0:f1f0::/48RIPENo 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.