bgpreport

Network · data from 2026-11-12

AS204903 FlashStart

Registry name: ColliniGroup FLASHSTART GROUP SRL, IT · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204903, 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.
185.236.106.0/24 Valid RIR databaseRIPE 671 100% 67
185.236.104.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
185.236.105.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
185.236.107.0/24 Valid RIR databaseRIPE 669 99% 67
67.217.251.0/24 Valid RIR databaseARIN, RADB 668 99% 67
2a12:7bc0:104::/48 Valid RIR databaseRADB, RIPE 634 100% 69
2a12:7bc0:105::/48 Valid RIR databaseRADB, RIPE 634 100% 69
2a12:7bc0:102::/48 Valid RIR databaseRIPE 633 100% 68
2a12:7bc0:103::/48 Valid RIR databaseRADB, RIPE 632 99% 68

AS-SET

AS204903'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 2 are in fix.csv.

  • Route object: not announced2

Route objects not announced

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

185.236.104.0/22RIPEValid
2a12:7bc0::/32RADB, RIPEValid

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.