bgpreport

Network · data from 2026-11-12

AS3311 tamkeentech-it Tamkeen Technologies LLC

Registry name: tamkeentech-it Tamkeen Technologies LLC, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3311, 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.
2a0e:3100:1000::/36 No ROA None 0 0%low visibility 1
2a0e:3100:6000::/36 No ROA None 0 0%low visibility 1
2a0e:3100::/36 Valid None 635 100% 67
185.106.244.0/24 Valid RIR databaseRIPE 673 100% 67
185.118.120.0/24 Valid RIR databaseRIPE 673 100% 67
185.118.122.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.118.123.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.106.246.0/24 Valid RIR databaseRIPE 672 100% 67
185.106.247.0/24 Valid RIR databaseRIPE 672 100% 67
185.106.245.0/24 Valid RIR databaseRIPE 671 100% 67
185.118.121.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS3311 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 5 are in fix.csv.

  • ROA: none2
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:3100:1000::/36No ROA covers it. Add a ROA for AS3311, maxLength 36.0 of 636
Route object: none2a0e:3100:1000::/36No route object for it. Add a route object with origin AS3311 in the RIR database for the space.0 of 636
ROA: none2a0e:3100:6000::/36No ROA covers it. Add a ROA for AS3311, maxLength 36.0 of 636
Route object: none2a0e:3100:6000::/36No route object for it. Add a route object with origin AS3311 in the RIR database for the space.0 of 636
Route object: none2a0e:3100::/36No route object for it. Add a route object with origin AS3311 in the RIR database for the space.635 of 636

Route objects not announced

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