bgpreport

Network · data from 2026-11-12

AS50398 FASTCOMMUNICATIONS

Registry name: FASTCOMMUNICATIONS Fast Communication, s.r.o., CZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS50398, 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.245.0.0/21 No ROA None 673 100% 66
91.219.44.0/22 Valid RIR databaseRIPE 673 100% 66
91.245.0.0/22 Valid RIR databaseRIPE 673 100% 66
91.245.4.0/24 Valid RIR databaseRIPE 673 100% 66
91.245.5.0/24 Valid RIR databaseRIPE 673 100% 66
91.245.6.0/24 Valid RIR databaseRIPE 673 100% 66
91.245.7.0/24 Valid RIR databaseRIPE 673 100% 66
2001:67c:1260::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS50398'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 8 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none91.245.0.0/21No ROA covers it. Add a ROA for AS50398, maxLength 21.673 of 673
Route object: none91.245.0.0/21No route object for it. Add a route object with origin AS50398 in the RIR database for the space.673 of 673

Route objects not announced

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

91.245.0.0/24RIPEValid
91.245.1.0/24RIPEValid
91.245.2.0/24RIPEValid
91.245.3.0/24RIPEValid
91.245.4.0/23RIPENo ROA
91.245.6.0/23RIPEValid

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.