bgpreport

Network · data from 2026-11-12

AS197703 FIRST-SERVER-AE IP MARKET - FZCO

Registry name: FIRST-SERVER-AE IP MARKET - FZCO, AE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197703, 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.
2a06:de06:387::/48 No ROA RIR databaseRIPE 634 100% 68
46.8.124.0/23 Valid RIR databaseRADB, RIPE 673 100% 66
135.136.182.0/23 Valid RIR databaseRADB, RIPE 673 100% 66
91.186.200.0/23 Valid RIR databaseRIPE 672 100% 66
94.241.162.0/24 Valid RIR databaseRIPE 671 100% 67
94.241.163.0/24 Valid RIR databaseRIPE 671 100% 67
132.243.30.0/23 Valid RIR databaseRIPE 671 100% 67
157.228.156.0/24 Valid RIR databaseRIPE 671 100% 67
157.228.176.0/23 Valid RIR databaseRIPE 671 100% 67
157.228.157.0/24 Valid RIR databaseRIPE 670 100% 67
2a0c:5d00:3011::/48 Valid RIR databaseRADB, RIPE 635 100% 68
2a0c:5d00:3012::/48 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: none1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none2a06:de06:387::/48No ROA covers it. Add a ROA for AS197703, maxLength 48.634 of 636

Route objects not announced

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

46.8.124.0/24RIPEValid
46.8.125.0/24RIPEValid
91.186.200.0/24RIPEValid
91.186.201.0/24RIPEValid
94.241.162.0/23RIPEValid
135.136.182.0/24RIPEValid
135.136.183.0/24RIPEValid
157.228.130.0/23RIPEValid
157.228.130.0/24RIPEValid
157.228.131.0/24RIPEValid
157.228.156.0/23RIPEValid
157.228.176.0/24RIPEValid
157.228.177.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.