bgpreport

Network · data from 2026-11-12

AS213812 alfateh Abdul Rahman Mustafa trading as Alfateh Company for Communications

Registry name: alfateh Abdul Rahman Mustafa trading as Alfateh Company for Communications, SY · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213812, 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.
38.19.194.0/23 Invalid: origin None 35 5%low visibility 22
87.232.124.0/24 Valid RIR databaseRIPE 673 100% 66
185.146.138.0/24 Valid RIR databaseRIPE 673 100% 66
185.146.139.0/24 Valid RIR databaseRIPE 673 100% 66
195.123.190.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS213812 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 6 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin38.19.194.0/23An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS213812 should announce it, add a ROA for AS213812.35 of 673
Route object: none38.19.194.0/23No route object for it. Add a route object with origin AS213812 in the RIR database for the space.35 of 673

Route objects not announced

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

185.146.138.0/23RIPENo ROA
185.220.168.0/23RIPENo ROA
185.220.168.0/24RIPENo ROA
185.220.169.0/24RIPENo 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.