bgpreport

Network · data from 2026-11-12

AS215496 DyarWeb DyarWeb Information Technology Ltd

Registry name: DyarWeb DyarWeb Information Technology Ltd, IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS215496, 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.
87.107.80.0/24 Invalid: origin None 101 15% 42
85.133.227.0/24 Invalid: origin None 2 0%low visibility 2
94.184.38.0/24 Valid RIR databaseRIPE 671 100% 66
185.124.173.0/24 Valid RIR databaseRIPE 671 100% 66
185.215.230.0/24 Valid RIR databaseRIPE 671 100% 66
85.133.206.0/24 Valid RIR databaseRIPE 670 100% 66
85.133.254.0/24 Valid RIR databaseRIPE 670 100% 66
94.183.211.0/24 Valid RIR databaseRIPE 670 100% 66
94.184.31.0/24 Valid RIR databaseRIPE 670 100% 66
185.118.12.0/24 Valid RIR databaseRIPE 670 100% 66
185.136.135.0/24 Valid RIR databaseRIPE 670 100% 66
2a05:9080:2::/48 Valid RIR databaseRIPE 635 100% 67
2a05:9080:12::/48 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS215496 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 4 are in fix.csv.

  • ROA: origin2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin87.107.80.0/24ROAs covering it name AS42337, AS43415, not AS215496. If AS215496 should announce it, add a ROA for AS215496.101 of 673
Route object: none87.107.80.0/24No route object for it. Add a route object with origin AS215496 in the RIR database for the space.101 of 673
ROA: origin85.133.227.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS215496 should announce it, add a ROA for AS215496.2 of 673
Route object: none85.133.227.0/24No route object for it. Add a route object with origin AS215496 in the RIR database for the space.2 of 673

Route objects not announced

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