bgpreport

Network · data from 2026-11-12

AS2118 RELCOM-AS Reliable Communications s.r.o.

Registry name: RELCOM-AS Reliable Communications s.r.o., CZ · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2118, 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.
192.124.179.0/24 Invalid: origin Other origin only 0 0%low visibility 1
193.124.23.0/24 No ROA RIR databaseRIPE 673 100% 66
193.124.34.0/24 No ROA RIR databaseRIPE 673 100% 66
193.124.50.0/24 No ROA RIR databaseRIPE 673 100% 66
193.124.60.0/24 No ROA RIR databaseRIPE 673 100% 66
194.58.82.0/24 No ROA RIR databaseRIPE 673 100% 66
194.58.83.0/24 No ROA RIR databaseRIPE 673 100% 66
194.58.246.0/24 No ROA RIR databaseRIPE 673 100% 66
194.87.5.0/24 No ROA RIR databaseRIPE 673 100% 66
194.87.50.0/24 No ROA RIR databaseRIPE 673 100% 66
194.87.241.0/24 No ROA RIR databaseRIPE 673 100% 66
194.87.247.0/24 No ROA RIR databaseRIPE 673 100% 66
194.87.249.0/24 No ROA RIR databaseRIPE 673 100% 66
194.135.35.0/24 No ROA RIR databaseRIPE 673 100% 66
195.133.87.0/24 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS2118 isn't in PeeringDB, where networks name their 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 17 are in fix.csv.

  • ROA: origin1
  • ROA: none14
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin192.124.179.0/24ROAs covering it name AS21082, not AS2118. If AS2118 should announce it, add a ROA for AS2118.0 of 673
Route object: none192.124.179.0/24Route objects for it name AS21082. Add a route object with origin AS2118 in the RIR database for the space.0 of 673
ROA: none193.124.23.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none193.124.34.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none193.124.50.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none193.124.60.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.58.82.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.58.83.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.58.246.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.87.5.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.87.50.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.87.241.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.87.247.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.87.249.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none194.135.35.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673
ROA: none195.133.87.0/24No ROA covers it. Add a ROA for AS2118, maxLength 24.673 of 673

Route objects not announced

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

212.113.96.0/19RIPEInvalid: 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.