bgpreport

Network · data from 2026-11-12

AS208200 FastServers .IT Cloud Provider

Registry name: FASTSERVERS-IT-AS Konstantin Kirsanov, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208200, 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.
2a0f:b300:1111::/48 Valid Nonecovered by 2a0f:b300:1000::/36 635 100% 67
45.154.72.0/24 Valid RIR databaseRIPE 672 100% 66
45.154.73.0/24 Valid RIR databaseRIPE 672 100% 67
2a0f:b300:1000::/48 Valid RIR databaseRIPE 635 100% 67
2a0f:b300:1001::/48 Valid RIR databaseRIPE 635 100% 67
2a0f:b300:1002::/48 Valid RIR databaseRIPE 635 100% 67
2a0f:b300:b300::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS208200'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 5 are in fix.csv.

  • Route object: none1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none2a0f:b300:1111::/48No route object for it. A route object for 2a0f:b300:1000::/36 with origin AS208200 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208200 in the RIR database for the space.635 of 636

Route objects not announced

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

45.154.72.0/23RIPEValid
2a0f:b300::/36RIPEValid
2a0f:b300::/48RIPEValid
2a0f:b300:1000::/36RIPEValid

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.