bgpreport

Network · data from 2026-11-12

AS45580 OMITECHINT-PH - 14413 Elmbrook Drive

Registry name: OMITECHINT-PH - 14413 Elmbrook Drive, PH · not in PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
17Route objects not announced registered with origin AS45580, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45580, 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.
182.239.32.0/23 Valid RIR databaseAPNIC, RADB 673 100% 68
182.239.32.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
182.239.33.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68

AS-SET

AS45580 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 17 are in fix.csv.

  • Route object: not announced17

Route objects not announced

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

123.108.112.0/20APNICNo ROA
123.108.112.0/24APNICInvalid: origin
123.108.113.0/24APNICInvalid: origin
123.108.114.0/24APNICInvalid: origin
123.108.115.0/24APNICInvalid: origin
123.108.116.0/24APNICNo ROA
123.108.117.0/24APNICNo ROA
123.108.118.0/24APNICNo ROA
123.108.119.0/24APNICNo ROA
123.108.120.0/24APNICInvalid: origin
123.108.121.0/24APNICInvalid: origin
123.108.122.0/24APNICInvalid: origin
123.108.123.0/24APNICInvalid: origin
123.108.124.0/24APNICInvalid: origin
123.108.125.0/24APNICInvalid: origin
123.108.126.0/24APNICInvalid: origin
123.108.127.0/24APNICInvalid: origin

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.