bgpreport

Network · data from 2026-11-12

AS48678 PENDC

Registry name: TR-PENTECH-AS Pentech Bilisim Teknolojileri Sanayi Ve Ticaret Limited Sirketi, TR · PeeringDB

55IPv4 routes 80.0% RPKI valid · 78.2% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
6RPKI invalid 6 origin · 0 maxLength
5No ROA 12 with no route object for this origin
20Low visibility seen by under 10% of full-table peers
93Route objects not announced registered with origin AS48678, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48678, 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.7.241.0/24 Invalid: origin None 2 0%low visibility 2
188.132.146.0/24 Invalid: origin None 2 0%low visibility 2
5.181.85.0/24 Invalid: origin Other origin only 1 0%low visibility 1
45.141.149.0/24 Invalid: origin Other origin only 1 0%low visibility 1
185.1.48.0/24 Invalid: origin None 1 0%low visibility 2
185.1.221.0/24 Invalid: origin Other origin only 1 0%low visibility 2
10.10.52.0/22 bogon No ROA None 1 0%low visibility 2
192.168.100.0/24 bogon No ROA Other origin only 1 0%low visibility 2
31.58.200.0/22 No ROA None 664 99% 67
31.58.176.0/22 No ROA None 2 0%low visibility 2
31.59.124.0/22 No ROA None 2 0%low visibility 2
188.132.153.0/24 Valid Other origin only 670 100% 67
31.210.48.0/24 Valid RIR databaseRIPE 670 100% 67
85.153.142.0/24 Valid RIR databaseRIPE 670 100% 67
149.3.171.0/24 Valid RIR databaseRIPE 670 100% 67
185.17.139.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.199.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.201.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.213.0/24 Valid RIR databaseRIPE 670 100% 67
188.132.235.0/24 Valid RIR databaseRIPE 670 100% 67
194.26.114.0/24 Valid RIR databaseRIPE 670 100% 67
195.24.232.0/24 Valid RIR databaseRIPE 670 100% 67
212.68.60.0/24 Valid RIR databaseRIPE 670 100% 67
212.115.30.0/24 Valid RIR databaseRIPE 670 100% 67
45.11.97.0/24 Valid RIR databaseRIPE 669 99% 67
45.11.98.0/24 Valid RIR databaseRIPE 669 99% 67
45.11.99.0/24 Valid RIR databaseRIPE 669 99% 67
62.106.94.0/24 Valid RIR databaseRIPE 669 99% 67
77.92.146.0/24 Valid RIR databaseRIPE 669 99% 67
78.135.66.0/24 Valid RIR databaseRIPE 669 99% 67
78.135.72.0/24 Valid RIR databaseRIPE 669 99% 67
78.135.104.0/24 Valid RIR databaseRIPE 669 99% 67
134.255.199.0/24 Valid RIR databaseRIPE 669 99% 67
178.211.130.0/24 Valid RIR databaseRIPE 669 99% 67
185.229.15.0/24 Valid RIR databaseRIPE 669 99% 67
185.231.110.0/24 Valid RIR databaseRIPE 669 99% 67
188.132.185.0/24 Valid RIR databaseRIPE 669 99% 67
188.132.189.0/24 Valid RIR databaseRIPE 669 99% 67
188.132.209.0/24 Valid RIR databaseRIPE 669 99% 67
188.132.212.0/24 Valid RIR databaseRIPE 669 99% 67
194.26.115.0/24 Valid RIR databaseRIPE 669 99% 67
212.98.224.0/24 Valid RIR databaseRIPE 669 99% 67
45.11.96.0/24 Valid RIR databaseRIPE 668 99% 67
81.18.55.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
176.96.130.0/24 Valid RIR databaseRIPE 668 99% 67
2a0c:6d40::/29 Valid RIR databaseRIPE 634 100% 67
185.106.22.0/24 Valid RIR databaseRIPE 4 1%low visibility 4
185.106.23.0/24 Valid RIR databaseRIPE 4 1%low visibility 4
78.135.100.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.28.61.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
188.93.141.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
188.132.186.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
188.132.234.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
212.68.58.0/24 Valid RIR databaseRIPE 2 0%low visibility 2
185.103.198.0/24 Valid RIR databaseRIPE 1 0%low visibility 1
185.106.21.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS48678: AS-PENTECH. 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 (AS48678 isn't in the set, or no route object for AS48678 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 objectsAS48678 in itNot covered
AS-PENTECH RIPElists itself further down 157233,982 Yes 12

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

  • ROA: origin6
  • Bogon prefix2
  • ROA: none3
  • Route object: none10
  • Route object: not announced93
ChangePrefix or setDetailFull-table peers
ROA: origin185.7.241.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS48678 should announce it, add a ROA for AS48678.2 of 673
Route object: none185.7.241.0/24No route object for it. Add a route object with origin AS48678 in the RIR database for the space.2 of 673
ROA: origin188.132.146.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS48678 should announce it, add a ROA for AS48678.2 of 673
Route object: none188.132.146.0/24No route object for it. Add a route object with origin AS48678 in the RIR database for the space.2 of 673
ROA: origin5.181.85.0/24ROAs covering it name AS211422, not AS48678. If AS48678 should announce it, add a ROA for AS48678.1 of 673
Route object: none5.181.85.0/24Route objects for it name AS211422. Add a route object with origin AS48678 in the RIR database for the space.1 of 673
ROA: origin45.141.149.0/24ROAs covering it name AS44547, not AS48678. If AS48678 should announce it, add a ROA for AS48678.1 of 673
Route object: none45.141.149.0/24Route objects for it name AS44547. Add a route object with origin AS48678 in the RIR database for the space.1 of 673
ROA: origin185.1.48.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS48678 should announce it, add a ROA for AS48678.1 of 673
Route object: none185.1.48.0/24No route object for it. Add a route object with origin AS48678 in the RIR database for the space.1 of 673
ROA: origin185.1.221.0/24ROAs covering it name AS59510, not AS48678. If AS48678 should announce it, add a ROA for AS48678.1 of 673
Route object: none185.1.221.0/24Route objects for it name AS59510, AS208972. Add a route object with origin AS48678 in the RIR database for the space.1 of 673
Bogon prefix10.10.52.0/22In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
Bogon prefix192.168.100.0/24In IANA's special-purpose registry: Private-Use (RFC 1918).1 of 673
ROA: none31.58.200.0/22No ROA covers it. Add a ROA for AS48678, maxLength 22.664 of 673
Route object: none31.58.200.0/22No route object for it. Add a route object with origin AS48678 in the RIR database for the space.664 of 673
ROA: none31.58.176.0/22No ROA covers it. Add a ROA for AS48678, maxLength 22.2 of 673
Route object: none31.58.176.0/22No route object for it. Add a route object with origin AS48678 in the RIR database for the space.2 of 673
ROA: none31.59.124.0/22No ROA covers it. Add a ROA for AS48678, maxLength 22.2 of 673
Route object: none31.59.124.0/22No route object for it. Add a route object with origin AS48678 in the RIR database for the space.2 of 673
Route object: none188.132.153.0/24Route objects for it name AS211804. Add a route object with origin AS48678 in the RIR database for the space.670 of 673

Route objects not announced

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

2.56.108.0/24RIPEValid
2.56.109.0/24RIPEValid
5.180.81.0/24RADB, RIPEValid
13.143.211.0/24RIPEValid
13.143.218.0/24RIPEValid
13.143.226.0/24RIPEValid
13.143.238.0/24RIPEValid
13.143.250.0/24RIPEValid
31.57.135.0/24RIPEInvalid: origin
31.58.245.0/24RIPEValid
31.77.58.0/24RIPEValid
31.210.50.0/24RIPEValid
45.59.70.0/24ARIN, RADBValid
45.81.113.0/24RIPEValid
45.81.115.0/24RIPEValid
45.88.139.0/24RIPEValid
45.132.181.0/24RIPEValid
45.192.19.0/24AFRINICInvalid: origin
46.36.201.0/24RIPEValid
77.83.37.0/24RIPEValid
77.83.202.0/24RIPEInvalid: origin
77.92.145.0/24RIPEValid
78.17.182.0/24RIPEValid
78.17.255.0/24RIPEValid
78.135.93.0/24RIPEValid
79.110.234.0/24RIPEValid
80.208.216.0/21RADBNo ROA
85.209.120.0/24RIPEValid
86.105.4.0/24RIPEValid
89.35.52.0/24RIPEInvalid: origin
89.125.20.0/24RIPEValid
89.125.252.0/24RIPEValid
91.208.204.0/24RIPEValid
104.143.203.0/24RIPEValid
104.143.216.0/24RIPEValid
132.243.72.0/24RIPEValid
132.243.75.0/24RIPEValid
141.98.48.0/24RIPEValid
162.35.226.0/24RIPEValid
162.35.228.0/24RIPEValid
163.5.39.0/24RIPEValid
163.5.53.0/24RADB, RIPEValid
163.5.66.0/24RIPEValid
163.5.182.0/24RIPEValid
163.5.237.0/24RIPEValid
163.5.246.0/24RIPEValid
185.28.60.0/24RIPEValid
185.28.63.0/24RIPEValid
185.81.153.0/24RIPEValid
185.103.196.0/24RIPEValid
185.103.197.0/24RIPEValid
185.103.199.0/24RIPEValid
185.106.20.0/24RIPEValid
185.157.46.0/24RADB, RIPEValid
185.158.151.0/24RADB, RIPEValid
185.176.95.0/24RIPEValid
185.223.77.0/24RADB, RIPEValid
185.233.164.0/24RADB, RIPEValid
185.246.113.0/24RADB, RIPEValid
185.254.29.0/24RIPEValid
188.132.129.0/24RIPEValid
188.132.152.0/24RIPEValid
188.132.168.0/24RIPEValid
188.132.183.0/24RIPEValid
188.132.184.0/24RIPEValid
192.124.188.0/24RIPEValid
193.35.152.0/24RIPEValid
193.57.41.0/24RIPEValid
193.111.125.0/24RADB, RIPEValid
193.160.222.0/24RIPEInvalid: origin
194.15.52.0/24RIPEValid
194.87.75.0/24RIPEValid
194.87.229.0/24RIPEValid
195.133.43.0/24RIPEValid
195.133.95.0/24RIPEValid
201.10.81.0/24RIPEValid
201.10.95.0/24RIPEValid
212.192.10.0/24RIPEValid
212.192.209.0/24RIPEValid
212.192.252.0/24RIPEValid
217.18.209.0/24RIPEValid
217.60.187.0/24RIPEValid
2a07:d800::/34RADBNo ROA
2a07:d801::/34RADBNo ROA
2a07:d802::/34RADBNo ROA
2a07:d803::/34RADBNo ROA
2a07:d804::/34RADBNo ROA
2a07:d805::/34RADBNo ROA
2a07:d806::/34RADBNo ROA
2a07:d807::/34RADBNo ROA
2a0f:eb05::/32RIPEInvalid: origin
2a0f:eb07::/32RIPEInvalid: origin
2a13:9500:102::/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.