bgpreport

Network · data from 2026-11-12

AS8462 Tarr Ltd.

Registry name: TARR1 Tarr Kft., HU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS8462, 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.
46.249.128.0/19 Valid RIR databaseRIPE 673 100% 67
77.110.128.0/19 Valid RIR databaseRIPE 673 100% 67
77.110.160.0/19 Valid RIR databaseRIPE 673 100% 67
77.111.128.0/18 Valid RIR databaseRIPE 673 100% 67
79.121.104.0/21 Valid RIR databaseRIPE 673 100% 67
79.121.112.0/21 Valid RIR databaseRIPE 673 100% 67
91.146.128.0/18 Valid RIR databaseRIPE 673 100% 67
95.168.32.0/19 Valid RIR databaseRIPE 673 100% 67
95.168.64.0/19 Valid RIR databaseRIPE 673 100% 67
185.3.136.0/22 Valid RIR databaseRIPE 673 100% 67
185.165.108.0/22 Valid RIR databaseRIPE 673 100% 67
185.166.132.0/22 Valid RIR databaseRIPE 673 100% 67
185.166.136.0/22 Valid RIR databaseRIPE 673 100% 67
185.170.84.0/22 Valid RIR databaseRIPE 673 100% 67
185.172.44.0/22 Valid RIR databaseRIPE 673 100% 67
185.187.248.0/22 Valid RIR databaseRIPE 673 100% 67
185.195.52.0/22 Valid RIR databaseRIPE 673 100% 67
185.202.136.0/22 Valid RIR databaseRIPE 673 100% 67
185.214.28.0/22 Valid RIR databaseRIPE 673 100% 67
185.224.4.0/22 Valid RIR databaseRIPE 673 100% 67
185.235.112.0/22 Valid RIR databaseRIPE 673 100% 67
193.151.116.0/22 Valid RIR databaseRIPE 673 100% 67
193.218.98.0/24 Valid RIR databaseRIPE 673 100% 67
193.227.196.0/22 Valid RIR databaseRIPE 673 100% 67
194.37.88.0/22 Valid RIR databaseRIPE 673 100% 67
195.128.232.0/23 Valid RIR databaseRIPE 673 100% 67
212.16.128.0/19 Valid RIR databaseRIPE 673 100% 67
2a01:5d0::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS8462'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 9 are in fix.csv.

  • Route object: not announced9

Route objects not announced

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

91.146.128.0/19RIPEInvalid: maxLength
91.146.160.0/21RIPEInvalid: maxLength
91.146.176.0/21RIPEInvalid: maxLength
91.146.184.0/22RIPEInvalid: maxLength
102.46.0.0/18AFRINICInvalid: origin
102.46.64.0/18AFRINICInvalid: origin
102.46.128.0/18AFRINICInvalid: origin
102.46.192.0/18AFRINICInvalid: origin
212.16.156.0/22RIPEInvalid: maxLength

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.