bgpreport

Network · data from 2026-11-12

AS202759 FairyHosting RJ Network OU

Registry name: FairyHosting RJ Network OU, EE · not in PeeringDB

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

Announced routes

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

185.158.135.0/24 Invalid: origin Other origin only 1 0%low visibility 1
93.89.218.0/24 No ROA Other origin only 2 0%low visibility 2
141.105.140.0/24 No ROA RIR databaseRIPE 673 100% 67
185.155.96.0/24 No ROA RIR databaseRIPE 673 100% 67
185.155.97.0/24 No ROA RIR databaseRIPE 673 100% 67
185.155.98.0/24 No ROA RIR databaseRIPE 673 100% 67
185.155.99.0/24 No ROA RIR databaseRIPE 673 100% 67
185.215.184.0/24 No ROA RIR databaseRIPE 673 100% 67
185.215.185.0/24 No ROA RIR databaseRIPE 673 100% 67
185.215.186.0/24 No ROA RIR databaseRIPE 673 100% 67
185.215.187.0/24 No ROA RIR databaseRIPE 673 100% 67
5.253.176.0/24 No ROA RIR databaseRIPE 672 100% 67
5.253.177.0/24 No ROA RIR databaseRIPE 672 100% 67
5.253.178.0/24 No ROA RIR databaseRIPE 672 100% 67
5.253.179.0/24 No ROA RIR databaseRIPE 672 100% 67
2a07:9280::/29 No ROA RIR databaseRIPE 635 100% 67
2a09:5840::/29 No ROA RIR databaseRIPE 635 100% 67
83.172.139.0/24 Valid RIR databaseRIPE 673 100% 67
89.40.104.0/24 Valid RIR databaseRIPE 673 100% 67
89.106.88.0/24 Valid RIR databaseRIPE 673 100% 67
93.113.98.0/24 Valid RIR databaseRIPE 673 100% 67
93.113.214.0/24 Valid RIR databaseRIPE 673 100% 67
95.156.206.0/24 Valid RIR databaseRIPE 673 100% 67
185.87.56.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.122.185.0/24 Valid RIR databaseRIPE 673 100% 67
185.155.55.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.155.222.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.193.49.0/24 Valid RIR databaseRIPE 673 100% 67
188.190.18.0/24 Valid RIR databaseRIPE 673 100% 67
188.214.32.0/24 Valid RIR databaseRIPE 673 100% 67
188.214.36.0/24 Valid RIR databaseRIPE 673 100% 67
188.214.37.0/24 Valid RIR databaseRIPE 673 100% 67
213.111.179.0/24 Valid RIR databaseRIPE 673 100% 67
213.111.181.0/24 Valid RIR databaseRIPE 673 100% 67
213.111.189.0/24 Valid RIR databaseRIPE 673 100% 67
213.111.190.0/24 Valid RIR databaseRIPE 673 100% 67
45.151.72.0/24 Valid RIR databaseRIPE 672 100% 67
185.93.33.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
2a03:f80:372::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS202759 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 21 are in fix.csv.

  • ROA: origin1
  • ROA: none16
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin185.158.135.0/24ROAs covering it name AS834, not AS202759. If AS202759 should announce it, add a ROA for AS202759.1 of 673
Route object: none185.158.135.0/24Route objects for it name AS834. Add a route object with origin AS202759 in the RIR database for the space.1 of 673
ROA: none93.89.218.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.2 of 673
Route object: none93.89.218.0/24Route objects for it name AS26383, AS59878, AS398343. Add a route object with origin AS202759 in the RIR database for the space.2 of 673
ROA: none141.105.140.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.155.96.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.155.97.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.155.98.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.155.99.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.215.184.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.215.185.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.215.186.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none185.215.187.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.673 of 673
ROA: none5.253.176.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.672 of 673
ROA: none5.253.177.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.672 of 673
ROA: none5.253.178.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.672 of 673
ROA: none5.253.179.0/24No ROA covers it. Add a ROA for AS202759, maxLength 24.672 of 673
ROA: none2a07:9280::/29No ROA covers it. Add a ROA for AS202759, maxLength 29.635 of 636
ROA: none2a09:5840::/29No ROA covers it. Add a ROA for AS202759, maxLength 29.635 of 636

Route objects not announced

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

185.155.96.0/22RIPENo ROA
194.156.99.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.