bgpreport

Network · data from 2026-11-12

AS215761 MFATIHASAN Muhammed Fatih ASAN

Registry name: MFATIHASAN Muhammed Fatih ASAN, TR · not in PeeringDB

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

Announced routes

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

45.197.10.0/24 Invalid: origin Other origin only 20 3%low visibility 16
5.83.209.0/24 Invalid: origin Other origin only 9 1%low visibility 10
2a12:bec4:1c00::/48 Invalid: origin Other origin only 7 1%low visibility 9
2a0f:85c1:7f5::/48 No ROA None 635 100% 67
13.143.222.0/24 Valid RIR databaseRIPE 672 100% 66
45.138.183.0/24 Valid RIR databaseRIPE 672 100% 66
45.144.214.0/24 Valid RIR databaseRIPE 670 100% 66

AS-SET

AS215761 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 8 are in fix.csv.

  • ROA: origin3
  • ROA: none1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin45.197.10.0/24ROAs covering it name AS17561, AS401783, not AS215761. If AS215761 should announce it, add a ROA for AS215761.20 of 673
Route object: none45.197.10.0/24Route objects for it name AS39600, AS401783. Add a route object with origin AS215761 in the RIR database for the space.20 of 673
ROA: origin5.83.209.0/24ROAs covering it name AS14618, AS16509, not AS215761. If AS215761 should announce it, add a ROA for AS215761.9 of 673
Route object: none5.83.209.0/24Route objects for it name AS16509. Add a route object with origin AS215761 in the RIR database for the space.9 of 673
ROA: origin2a12:bec4:1c00::/48ROAs covering it name AS213535, not AS215761. If AS215761 should announce it, add a ROA for AS215761.7 of 636
Route object: none2a12:bec4:1c00::/48Route objects for it name AS213535. Add a route object with origin AS215761 in the RIR database for the space.7 of 636
ROA: none2a0f:85c1:7f5::/48No ROA covers it. Add a ROA for AS215761, maxLength 48.635 of 636
Route object: none2a0f:85c1:7f5::/48No route object for it. Add a route object with origin AS215761 in the RIR database for the space.635 of 636

Route objects not announced

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