bgpreport

Network · data from 2026-11-12

AS10076 Erdemnet MNREN

Registry name: ASN-ERDEMNET # AS-ERDEMNET converted to ASN-ERDEMNET for RPSL compliance - ERDEMNET Mongolian National Research and Education Network, MN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS10076, 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.
202.5.201.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
161.248.142.0/23 Valid RIR databaseAPNIC 669 99% 68
202.5.192.0/20 Valid RIR databaseAPNIC, RADB 669 99% 68
202.5.193.0/24 Valid RIR databaseAPNIC, RADB 669 99% 68
2404:ec80::/32 Valid RIR databaseAPNIC 635 100% 68
202.5.196.0/24 Valid RIR databaseAPNIC, RADB 16 2%low visibility 17

AS-SET

AS10076's PeeringDB record names no 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 28 are in fix.csv.

  • Route object: not announced28

Route objects not announced

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

202.5.192.0/21APNIC, RADBValid
202.5.192.0/22APNIC, RADBValid
202.5.192.0/23APNIC, RADBValid
202.5.192.0/24APNIC, RADBValid
202.5.192.28/32APNICValid
202.5.194.0/23APNIC, RADBValid
202.5.194.0/24APNIC, RADBValid
202.5.195.0/24APNIC, RADBValid
202.5.196.0/22APNIC, RADBValid
202.5.196.0/23APNIC, RADBValid
202.5.197.0/24APNIC, RADBValid
202.5.198.0/23APNIC, RADBValid
202.5.198.0/24APNIC, RADBValid
202.5.199.0/24APNIC, RADBValid
202.5.200.0/21APNIC, RADBValid
202.5.200.0/22APNIC, RADBValid
202.5.200.0/23APNIC, RADBValid
202.5.200.0/24APNIC, RADBValid
202.5.202.0/23APNIC, RADBValid
202.5.202.0/24APNIC, RADBValid
202.5.203.0/24APNIC, RADBValid
202.5.204.0/22APNIC, RADBValid
202.5.204.0/23APNIC, RADBValid
202.5.204.0/24APNIC, RADBValid
202.5.205.0/24APNIC, RADBValid
202.5.206.0/23APNIC, RADBValid
202.5.206.0/24APNIC, RADBValid
202.5.207.0/24APNIC, RADBValid

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.