bgpreport

Network · data from 2026-11-12

AS50360 4vendeta

Registry name: TAMATIYA-AS Tamatiya EOOD, BG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50360, 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.
79.124.59.190/32 Invalid: maxLength Nonecovered by 79.124.59.0/24 2 0%low visibility 6
195.230.25.0/24 No ROA RIR databaseRIPE 673 100% 66
195.230.24.0/24 No ROA RIR databaseRIPE 672 100% 67
2001:67c:15e0::/48 No ROA RIR databaseRIPE 634 100% 67
78.142.49.0/24 Valid RIR databaseRIPE 673 100% 66
79.124.40.0/24 Valid RIR databaseRIPE 673 100% 66
79.124.45.0/24 Valid RIR databaseRIPE 673 100% 66
79.124.56.0/24 Valid RIR databaseRIPE 673 100% 66
79.124.59.0/24 Valid RIR databaseRIPE 673 100% 66
79.124.60.0/24 Valid RIR databaseRIPE 673 100% 66
91.148.128.0/24 Valid RIR databaseRIPE 673 100% 66
91.148.129.0/24 Valid RIR databaseRIPE 673 100% 66
91.148.186.0/24 Valid RIR databaseRIPE 673 100% 66
91.148.190.0/24 Valid RIR databaseRIPE 673 100% 66
91.148.191.0/24 Valid RIR databaseRIPE 673 100% 66
91.191.220.0/24 Valid RIR databaseRIPE 673 100% 66
91.191.221.0/24 Valid RIR databaseRIPE 673 100% 66
91.191.222.0/24 Valid RIR databaseRIPE 673 100% 66
91.191.223.0/24 Valid RIR databaseRIPE 673 100% 66
5.181.80.0/24 Valid RIR databaseRIPE 672 100% 66
78.128.114.0/24 Valid RIR databaseRIPE 672 100% 67
79.124.41.0/24 Valid RIR databaseRIPE 672 100% 67
79.124.49.0/24 Valid RIR databaseRIPE 672 100% 67
83.222.190.0/24 Valid RIR databaseRIPE 672 100% 66
79.124.58.0/24 Valid RIR databaseRIPE 670 100% 66

AS-SET

AS50360'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 10 are in fix.csv.

  • ROA: maxLength1
  • ROA: none3
  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength79.124.59.190/32ROA 79.124.59.0/24 AS50360 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 79.124.59.190/32.2 of 673
Route object: none79.124.59.190/32No route object for it. A route object for 79.124.59.0/24 with origin AS50360 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS50360 in the RIR database for the space.2 of 673
ROA: none195.230.25.0/24No ROA covers it. Add a ROA for AS50360, maxLength 24.673 of 673
ROA: none195.230.24.0/24No ROA covers it. Add a ROA for AS50360, maxLength 24.672 of 673
ROA: none2001:67c:15e0::/48No ROA covers it. Add a ROA for AS50360, maxLength 48.634 of 636

Route objects not announced

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

78.142.35.0/24RIPEValid
79.124.62.0/24RIPEValid
85.187.226.0/24RIPEInvalid: origin
91.148.190.0/23RIPEValid
91.204.220.0/24RIPENo ROA

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.