bgpreport

Network · data from 2026-11-12

AS202412 OMEGATECH-AS Omegatech LTD

Registry name: OMEGATECH-AS Omegatech LTD, SC · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202412, 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.

45.132.180.0/24 Invalid: origin None 4 1%low visibility 3
91.92.240.0/24 Invalid: origin None 4 1%low visibility 3
91.92.241.0/24 Invalid: origin None 4 1%low visibility 3
91.92.242.0/24 Invalid: origin None 4 1%low visibility 3
91.92.243.0/24 Invalid: origin None 4 1%low visibility 3
94.154.35.0/24 Invalid: origin None 4 1%low visibility 3
94.154.46.0/24 Invalid: origin None 4 1%low visibility 3
146.19.125.0/24 Invalid: origin None 4 1%low visibility 3
158.94.208.0/24 Invalid: origin None 4 1%low visibility 3
158.94.209.0/24 Invalid: origin None 4 1%low visibility 3
158.94.210.0/24 Invalid: origin None 4 1%low visibility 3
158.94.211.0/24 Invalid: origin None 4 1%low visibility 3
178.16.52.0/24 Invalid: origin None 4 1%low visibility 4
178.16.53.0/24 Invalid: origin None 4 1%low visibility 4
178.16.54.0/24 Invalid: origin None 4 1%low visibility 5
178.16.55.0/24 Invalid: origin None 4 1%low visibility 4
193.30.241.0/24 Invalid: origin None 4 1%low visibility 3
94.154.40.0/24 Invalid: origin None 2 0%low visibility 1
172.111.246.0/24 No ROA Other origin only 2 0%low visibility 2
130.12.180.0/24 Valid RIR databaseARIN 4 1%low visibility 3

AS-SET

AS202412 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 38 are in fix.csv.

  • ROA: origin18
  • ROA: none1
  • Route object: none19
ChangePrefix or setDetailFull-table peers
ROA: origin45.132.180.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none45.132.180.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin91.92.240.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none91.92.240.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin91.92.241.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none91.92.241.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin91.92.242.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none91.92.242.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin91.92.243.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none91.92.243.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin94.154.35.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none94.154.35.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin94.154.46.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none94.154.46.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin146.19.125.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none146.19.125.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin158.94.208.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none158.94.208.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin158.94.209.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none158.94.209.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin158.94.210.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none158.94.210.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin158.94.211.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none158.94.211.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin178.16.52.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none178.16.52.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin178.16.53.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none178.16.53.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin178.16.54.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none178.16.54.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin178.16.55.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none178.16.55.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin193.30.241.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.4 of 673
Route object: none193.30.241.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.4 of 673
ROA: origin94.154.40.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS202412 should announce it, add a ROA for AS202412.2 of 673
Route object: none94.154.40.0/24No route object for it. Add a route object with origin AS202412 in the RIR database for the space.2 of 673
ROA: none172.111.246.0/24No ROA covers it. Add a ROA for AS202412, maxLength 24.2 of 673
Route object: none172.111.246.0/24Route objects for it name AS212238. Add a route object with origin AS202412 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS202412 is announced.

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.