bgpreport

Network · data from 2026-11-12

AS51248 Host-Telecom.com

Registry name: HOST-TELECOM Host-Telecom.com s.r.o., CZ · PeeringDB

37IPv4 routes 56.8% RPKI valid · 59.5% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
15RPKI invalid 9 origin · 6 maxLength
1No ROA 15 with no route object for this origin
15Low visibility seen by under 10% of full-table peers
21Route objects not announced registered with origin AS51248, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS51248, 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.

91.199.137.167/32 Invalid: origin None 2 0%low visibility 5
91.199.154.10/32 Invalid: origin None 2 0%low visibility 5
141.133.172.134/32 Invalid: origin None 2 0%low visibility 5
141.133.175.11/32 Invalid: origin None 2 0%low visibility 5
160.20.109.40/32 Invalid: origin None 2 0%low visibility 5
160.20.109.112/32 Invalid: origin None 2 0%low visibility 5
160.20.109.156/32 Invalid: origin None 2 0%low visibility 5
160.20.109.169/32 Invalid: origin None 2 0%low visibility 5
160.20.109.187/32 Invalid: origin None 2 0%low visibility 5
45.151.183.76/32 Invalid: maxLength Nonecovered by 45.151.183.0/24 2 0%low visibility 5
153.52.69.58/32 Invalid: maxLength Nonecovered by 153.52.69.0/24 2 0%low visibility 5
188.130.208.88/32 Invalid: maxLength Nonecovered by 188.130.208.0/24 2 0%low visibility 5
193.161.86.53/32 Invalid: maxLength Nonecovered by 193.161.84.0/22 2 0%low visibility 5
194.87.126.182/32 Invalid: maxLength Nonecovered by 194.87.126.0/24 2 0%low visibility 5
195.133.35.34/32 Invalid: maxLength Nonecovered by 195.133.35.0/24 2 0%low visibility 5
45.10.191.0/24 No ROA RIR databaseRIPE 671 100% 66
13.143.234.0/24 Valid RIR databaseRIPE 673 100% 67
85.137.25.0/24 Valid RIR databaseRIPE 673 100% 67
85.137.26.0/24 Valid RIR databaseRIPE 673 100% 67
89.125.237.0/24 Valid RIR databaseRIPE 673 100% 67
153.52.69.0/24 Valid RIR databaseRIPE 673 100% 67
194.87.52.0/24 Valid RIR databaseRIPE 673 100% 67
194.87.126.0/24 Valid RIR databaseRIPE 673 100% 67
195.133.35.0/24 Valid RIR databaseRIPE 673 100% 67
212.192.210.0/24 Valid RIR databaseRIPE 673 100% 67
5.43.224.0/21 Valid RIR databaseRIPE 672 100% 66
48.103.175.0/24 Valid RIR databaseRIPE 672 100% 67
91.209.77.0/24 Valid RIR databaseRIPE 672 100% 66
201.8.94.0/24 Valid RIR databaseRIPE 672 100% 67
45.129.142.0/24 Valid RIR databaseRIPE 671 100% 67
135.106.134.0/23 Valid RIR databaseRIPE 671 100% 66
158.255.32.0/21 Valid RIR databaseRIPE 671 100% 66
176.74.216.0/21 Valid RIR databaseRIPE 671 100% 66
188.124.56.0/21 Valid RIR databaseRIPE 671 100% 66
193.161.84.0/22 Valid RIR databaseRIPE 671 100% 66
185.8.56.0/22 Valid RIR databaseRIPE 670 100% 66
158.255.39.0/24 Valid RIR databaseRIPE 667 99% 67
2a03:1840::/48 Valid RIR databaseRIPE 636 100% 67
2a03:1840:1::/48 Valid RIR databaseRIPE 636 100% 67
2a03:1840:2::/48 Valid RIR databaseRIPE 636 100% 67
2a03:1840:3::/48 Valid RIR databaseRIPE 636 100% 67
2a10:9687::/32 Valid RIR databaseRIPE 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS51248: AS-HOST-TELECOM-CZ. 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 (AS51248 isn't in the set, or no route object for AS51248 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 objectsAS51248 in itNot covered
AS-HOST-TELECOM-CZ RIPE 81237 Yes 15

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

  • ROA: origin9
  • ROA: maxLength6
  • ROA: none1
  • Route object: none15
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: origin91.199.137.167/32ROAs covering it name AS62212, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none91.199.137.167/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin91.199.154.10/32ROAs covering it name AS62212, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none91.199.154.10/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin141.133.172.134/32ROAs covering it name AS62212, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none141.133.172.134/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin141.133.175.11/32ROAs covering it name AS62212, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none141.133.175.11/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin160.20.109.40/32ROAs covering it name AS402492, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none160.20.109.40/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin160.20.109.112/32ROAs covering it name AS402492, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none160.20.109.112/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin160.20.109.156/32ROAs covering it name AS402492, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none160.20.109.156/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin160.20.109.169/32ROAs covering it name AS402492, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none160.20.109.169/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: origin160.20.109.187/32ROAs covering it name AS402492, not AS51248. If AS51248 should announce it, add a ROA for AS51248.2 of 673
Route object: none160.20.109.187/32No route object for it. Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: maxLength45.151.183.76/32ROA 45.151.183.0/24 AS51248 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 45.151.183.76/32.2 of 673
Route object: none45.151.183.76/32No route object for it. A route object for 45.151.183.0/24 with origin AS51248 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: maxLength153.52.69.58/32ROA 153.52.69.0/24 AS51248 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 153.52.69.58/32.2 of 673
Route object: none153.52.69.58/32No route object for it. A route object for 153.52.69.0/24 with origin AS51248 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: maxLength188.130.208.88/32ROA 188.130.208.0/24 AS51248 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 188.130.208.88/32.2 of 673
Route object: none188.130.208.88/32No route object for it. A route object for 188.130.208.0/24 with origin AS51248 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: maxLength193.161.86.53/32ROA 193.161.84.0/22 AS51248 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 193.161.86.53/32.2 of 673
Route object: none193.161.86.53/32No route object for it. A route object for 193.161.84.0/22 with origin AS51248 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: maxLength194.87.126.182/32ROA 194.87.126.0/24 AS51248 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 194.87.126.182/32.2 of 673
Route object: none194.87.126.182/32No route object for it. A route object for 194.87.126.0/24 with origin AS51248 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: maxLength195.133.35.34/32ROA 195.133.35.0/24 AS51248 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 195.133.35.34/32.2 of 673
Route object: none195.133.35.34/32No route object for it. A route object for 195.133.35.0/24 with origin AS51248 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS51248 in the RIR database for the space.2 of 673
ROA: none45.10.191.0/24No ROA covers it. Add a ROA for AS51248, maxLength 24.671 of 673

Route objects not announced

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

5.43.224.0/24RIPEValid
5.43.225.0/24RIPEValid
5.43.226.0/24RIPEValid
5.43.227.0/24RIPEValid
5.43.228.0/24RIPEValid
5.43.229.0/24RIPEValid
5.43.230.0/24RIPEValid
5.43.231.0/24RIPEValid
45.151.183.0/24RIPEValid
46.8.113.0/24RIPEValid
85.137.27.0/24RIPEInvalid: origin
188.124.56.0/24RIPEValid
188.124.57.0/24RIPEValid
188.124.58.0/24RIPEValid
188.124.59.0/24RIPEValid
188.124.60.0/24RIPEValid
188.124.61.0/24RIPEValid
188.124.62.0/24RIPEValid
188.124.63.0/24RIPEValid
188.130.208.0/24RIPEValid
192.145.98.0/24RIPEValid

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.