bgpreport

Network · data from 2026-11-12

AS202505 Netbudur Istanbul Backbone

Registry name: NETBUDUR-DATACENTER-ISTANBUL Netbudur Telekomunikasyon Limited Sirketi, TR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202505, 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.
185.81.153.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a06:f7c0::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c1::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c2::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c3::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c4::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c5::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c6::/32 No ROA RIR databaseRIPE 635 100% 67
2a06:f7c7::/32 No ROA RIR databaseRIPE 635 100% 67
84.54.14.0/24 Valid Other origin only 673 100% 67
86.104.14.0/24 Valid RIR databaseRIPE 673 100% 67
89.43.78.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.42.0/24 Valid RIR databaseRIPE 673 100% 67
176.98.43.0/24 Valid RIR databaseRIPE 673 100% 67
185.81.152.0/24 Valid RIR databaseRIPE 673 100% 67
185.81.155.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

PeeringDB's irr_as_set for AS202505: AS-NETBUDUR. 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 (AS202505 isn't in the set, or no route object for AS202505 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 objectsAS202505 in itNot covered
AS-NETBUDUR RIPE 614,298 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: origin1
  • ROA: none8
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin185.81.153.0/24ROAs covering it name AS48678, AS203804, AS205463, AS213799, AS216192, AS219521, not AS202505; an AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202505 should announce it, add a ROA for AS202505.2 of 673
Route object: none185.81.153.0/24Route objects for it name AS48678, AS203804, AS205463, AS213799, AS216192, AS219521. Add a route object with origin AS202505 in the RIR database for the space.2 of 673
ROA: none2a06:f7c0::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c1::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c2::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c3::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c4::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c5::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c6::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
ROA: none2a06:f7c7::/32No ROA covers it. Add a ROA for AS202505, maxLength 32.635 of 636
Route object: none84.54.14.0/24Route objects for it name AS6205, AS61220. Add a route object with origin AS202505 in the RIR database for the space.673 of 673

Route objects not announced

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

2.59.117.0/24RIPEInvalid: 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.