bgpreport

Network · data from 2026-11-12

AS131467 EGNC-AS - Unified National Networks

Registry name: EGNC-AS - Unified National Networks, BN · 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
11Route objects not announced registered with origin AS131467, seen from no peer

Announced routes

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

103.4.188.0/22 Valid RIR databaseAPNIC 670 100% 66
103.4.189.0/24 Valid RIR databaseAPNIC 670 100% 66
103.4.190.0/24 Valid RIR databaseAPNIC 670 100% 66

AS-SET

AS131467 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 11 are in fix.csv.

  • Route object: not announced11

Route objects not announced

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

103.4.188.0/23APNICInvalid: maxLength
103.4.188.0/24APNICValid
103.4.190.0/23APNICInvalid: maxLength
103.4.191.0/24APNICValid
2406:7801::/32APNICNo ROA
2406:7801::/33APNICNo ROA
2406:7801::/34APNICNo ROA
2406:7801:4000::/34APNICNo ROA
2406:7801:8000::/33APNICNo ROA
2406:7801:8000::/34APNICNo ROA
2406:7801:c000::/34APNICNo 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.