bgpreport

Network · data from 2026-11-12

AS210574 Poyraz Hosting

Registry name: POYRAZ PH Bilisim Teknolojileri Limited Sirketi, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210574, 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.
141.98.112.0/24 Invalid: origin None 2 0%low visibility 2
141.98.115.0/24 Invalid: origin None 2 0%low visibility 2
5.180.81.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
5.250.253.0/24 Valid RIR databaseRIPE 673 100% 67
87.76.139.0/24 Valid RIR databaseRIPE 673 100% 67
185.223.77.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.111.125.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
213.238.180.0/24 Valid RIR databaseRIPE 673 100% 67
2.59.117.0/24 Valid RIR databaseRIPE 672 100% 67
45.59.70.0/24 Valid RIR databaseARIN, RADB 672 100% 67
46.36.201.0/24 Valid RIR databaseRIPE 672 100% 67
2a11:5dc0:1::/48 Valid RIR databaseRIPE 634 100% 67
2a11:5dc0:10::/48 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS210574: RIPE::AS210574:AS-POYRAZ. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS210574 isn't in the set, or no route object for AS210574 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS210574 in itNot covered
RIPE::AS210574:AS-POYRAZ RIPE 118143,041 Yes 2

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: origin2
  • Route object: none2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: origin141.98.112.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS210574 should announce it, add a ROA for AS210574.2 of 673
Route object: none141.98.112.0/24No route object for it. Add a route object with origin AS210574 in the RIR database for the space.2 of 673
ROA: origin141.98.115.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS210574 should announce it, add a ROA for AS210574.2 of 673
Route object: none141.98.115.0/24No route object for it. Add a route object with origin AS210574 in the RIR database for the space.2 of 673

Route objects not announced

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

2a11:5dc0:2::/48RIPEValid
2a11:5dc0:3::/48RIPEValid
2a11:5dc0:4::/48RIPEValid
2a11:5dc0:5::/48RIPEValid
2a11:5dc0:6::/48RIPEValid
2a11:5dc0:7::/48RIPEValid
2a11:5dc0:8::/48RIPEValid
2a11:5dc0:9::/48RIPEValid

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.