bgpreport

Network · data from 2026-11-12

AS205142 FLEX-AMF Flex Ltd.

Registry name: FLEX-AMF Flex Ltd., SG · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS205142, 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.
158.116.249.0/24 No ROA Other origin onlycovered by 158.116.248.0/22 673 100% 67
158.116.251.0/24 No ROA Other origin onlycovered by 158.116.250.0/23 670 100% 67
158.116.248.0/22 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67
158.116.250.0/23 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67
158.116.250.0/24 No ROA Other IRR onlyRIPE-NONAUTH 673 100% 67

AS-SET

AS205142 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: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none158.116.249.0/24No ROA covers it. Add a ROA for AS205142, maxLength 24.673 of 673
Route object: none158.116.249.0/24Route objects for it name AS18882. A route object for 158.116.248.0/22 with origin AS205142 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205142 in the RIR database for the space.673 of 673
ROA: none158.116.251.0/24No ROA covers it. Add a ROA for AS205142, maxLength 24.670 of 673
Route object: none158.116.251.0/24Route objects for it name AS18882. A route object for 158.116.250.0/23 with origin AS205142 covers it (filters allowing more-specifics accept it). Add a route object with origin AS205142 in the RIR database for the space.670 of 673
ROA: none158.116.248.0/22No ROA covers it. Add a ROA for AS205142, maxLength 22.673 of 673
Route object: RIR158.116.248.0/22Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none158.116.250.0/23No ROA covers it. Add a ROA for AS205142, maxLength 23.673 of 673
Route object: RIR158.116.250.0/23Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673
ROA: none158.116.250.0/24No ROA covers it. Add a ROA for AS205142, maxLength 24.673 of 673
Route object: RIR158.116.250.0/24Route object only in RIPE-NONAUTH. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

158.116.248.0/29RIPE-NONAUTHNo ROA
158.116.248.8/29RIPE-NONAUTHNo ROA
158.116.248.16/29RIPE-NONAUTHNo ROA
158.116.248.24/29RIPE-NONAUTHNo ROA

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.