bgpreport

Network · data from 2026-11-12

AS207474 HatNet

Registry name: HatNet Hatnet Bilgi iletisim Teknolojileri ve Ticaret Limited Sirketi, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207474, 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.
207.230.4.0/24 Invalid: origin None 19 3%low visibility 12
207.230.3.0/24 Invalid: origin RIR databaseARIN 19 3%low visibility 12
153.56.169.0/24 Valid RIR databaseRIPE 673 100% 67
131.222.207.0/24 Valid RIR databaseRIPE 671 100% 67
131.222.229.0/24 Valid RIR databaseRIPE 671 100% 67
131.222.223.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

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

  • ROA: origin2
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin207.230.4.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS207474 should announce it, add a ROA for AS207474.19 of 673
Route object: none207.230.4.0/24No route object for it. Add a route object with origin AS207474 in the RIR database for the space.19 of 673
ROA: origin207.230.3.0/24ROAs covering it name AS174, not AS207474. If AS207474 should announce it, add a ROA for AS207474.19 of 673

Route objects not announced

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

207.230.6.0/24ARINInvalid: origin
207.230.7.0/24ARINInvalid: origin

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.