bgpreport

Network · data from 2026-11-12

AS56582 NETFACTOR TELEKOMINIKASYON VE TEKNOLOJI HIZMETLERI SANAYI VE

Registry name: NETFACTOR-ASN Netfactor Telekominikasyon ve Teknoloji Hizmetleri San. ve Tic. A.S., TR · PeeringDB

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

Announced routes

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

31.169.80.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.210.177.0/24 No ROA None 672 100% 67
178.210.178.0/24 No ROA None 672 100% 67
185.33.63.0/24 Valid None 673 100% 66
31.169.74.0/24 Valid Other origin only 671 100% 67
31.169.64.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.65.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.66.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.67.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.69.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.70.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.71.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.72.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.77.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.78.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.79.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.81.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.82.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.84.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.85.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.87.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.88.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.90.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.92.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.94.0/24 Valid RIR databaseRIPE 673 100% 66
31.169.95.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.216.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.217.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.218.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.219.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.227.0/24 Valid RIR databaseRIPE 673 100% 66
131.222.228.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.160.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.170.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.171.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.172.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.173.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.174.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.175.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.176.0/24 Valid RIR databaseRIPE 673 100% 66
178.210.180.0/24 Valid RIR databaseRIPE 673 100% 66
217.70.11.0/24 Valid RIR databaseRIPE 673 100% 66
45.89.28.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
46.235.14.0/24 Valid RIR databaseRIPE 672 100% 66
80.245.47.0/24 Valid RIR databaseRIPE 672 100% 66
31.169.76.0/24 Valid RIR databaseRIPE 671 100% 67
31.169.93.0/24 Valid RIR databaseRIPE 671 100% 67
2a00:5740::/29 Valid RIR databaseRIPE 633 100% 67

AS-SET

AS56582's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none5
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin31.169.80.0/24ROAs covering it name AS15924, not AS56582. If AS56582 should announce it, add a ROA for AS56582.2 of 673
Route object: none31.169.80.0/24Route objects for it name AS15924. Add a route object with origin AS56582 in the RIR database for the space.2 of 673
ROA: none178.210.177.0/24No ROA covers it. Add a ROA for AS56582, maxLength 24.672 of 673
Route object: none178.210.177.0/24No route object for it. Add a route object with origin AS56582 in the RIR database for the space.672 of 673
ROA: none178.210.178.0/24No ROA covers it. Add a ROA for AS56582, maxLength 24.672 of 673
Route object: none178.210.178.0/24No route object for it. Add a route object with origin AS56582 in the RIR database for the space.672 of 673
Route object: none185.33.63.0/24No route object for it. Add a route object with origin AS56582 in the RIR database for the space.673 of 673
Route object: none31.169.74.0/24Route objects for it name AS34984. Add a route object with origin AS56582 in the RIR database for the space.671 of 673

Route objects not announced

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

31.169.86.0/24RIPEInvalid: origin
79.134.234.0/24RIPEValid
91.102.167.0/24RIPEInvalid: origin
212.87.196.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.