bgpreport

Network · data from 2026-11-12

AS133385 ATOM Myanmar

Registry name: ATOMMYANMAR-AS-AP - Atom Myanmar Limited, MM · PeeringDB

55IPv4 routes 100.0% RPKI valid · 100.0% with a route object
20IPv6 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
0Low visibility seen by under 10% of full-table peers
90Route objects not announced registered with origin AS133385, seen from no peer

Announced routes

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

37.111.8.0/21 Valid RIR databaseAPNIC 673 100% 66
37.111.43.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
37.111.0.0/21 Valid RIR databaseAPNIC, RADB 671 100% 66
37.111.0.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.8.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.9.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.10.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.11.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.12.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.13.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.14.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.15.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.41.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
37.111.44.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
37.111.46.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
37.111.56.0/24 Valid RIR databaseAPNIC 671 100% 66
37.111.1.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.2.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.3.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.4.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.5.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.6.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.7.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
37.111.32.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.34.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.40.0/22 Valid RIR databaseAPNIC 669 99% 66
37.111.40.0/24 Valid RIR databaseAPNIC 669 99% 67
37.111.42.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
37.111.48.0/22 Valid RIR databaseAPNIC 669 99% 66
37.111.48.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.49.0/24 Valid RIR databaseAPNIC 669 99% 67
37.111.50.0/24 Valid RIR databaseAPNIC 669 99% 67
37.111.51.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.52.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.60.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.63.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.85.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.86.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.87.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.88.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.124.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.125.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.126.0/24 Valid RIR databaseAPNIC 669 99% 66
37.111.127.0/24 Valid RIR databaseAPNIC 669 99% 66
45.120.84.0/22 Valid RIR databaseAPNIC, RADB 669 99% 66
45.120.84.0/24 Valid RIR databaseAPNIC 669 99% 66
45.120.85.0/24 Valid RIR databaseAPNIC 669 99% 66
45.120.86.0/24 Valid RIR databaseAPNIC 669 99% 66
45.120.87.0/24 Valid RIR databaseAPNIC 669 99% 66
103.255.172.0/22 Valid RIR databaseAPNIC, RADB 669 99% 66
103.255.172.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
103.255.173.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
103.255.174.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
103.255.175.0/24 Valid RIR databaseAPNIC, RADB 669 99% 66
37.111.53.0/24 Valid RIR databaseAPNIC 666 99% 66
2400:8480:1000::/48 Valid RIR databaseAPNIC 636 100% 67
2400:8480:1100::/48 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2010::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2020::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2030::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2040::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2110::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2120::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2130::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:2140::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3010::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3020::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3030::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3040::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3110::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3120::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3130::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:3140::/44 Valid RIR databaseAPNIC 636 100% 67
2400:8480:4000::/36 Valid RIR databaseAPNIC 636 100% 67
2400:8480:5000::/36 Valid RIR databaseAPNIC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS133385: AS133385:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133385 isn't in the set, or no route object for AS133385 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS133385 in itNot covered
AS133385:AS-CUSTOMERS APNIC 94129,522 Yes 0

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

  • Route object: not announced90

Route objects not announced

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

37.111.0.0/22APNICValid
37.111.4.0/22APNICValid
37.111.8.0/22APNICValid
37.111.12.0/22APNICValid
37.111.16.0/21APNICValid
37.111.16.0/22APNICValid
37.111.16.0/24APNICValid
37.111.17.0/24APNICValid
37.111.18.0/24APNICValid
37.111.19.0/24APNICValid
37.111.20.0/22APNICValid
37.111.20.0/24APNICValid
37.111.21.0/24APNICValid
37.111.22.0/24APNICValid
37.111.23.0/24APNICValid
37.111.32.0/21APNICValid
37.111.32.0/22APNICValid
37.111.32.0/23APNICValid
37.111.33.0/24APNICValid
37.111.34.0/23APNICValid
37.111.35.0/24APNICValid
37.111.36.0/22APNICValid
37.111.36.0/23APNICValid
37.111.36.0/24APNICValid
37.111.37.0/24APNICValid
37.111.38.0/23APNICValid
37.111.38.0/24APNICValid
37.111.39.0/24APNICValid
37.111.40.0/23APNICValid
37.111.42.0/23APNICValid
37.111.44.0/22APNICValid
37.111.44.0/23APNICValid
37.111.45.0/24APNICValid
37.111.46.0/23APNICValid
37.111.47.0/24APNICValid
37.111.48.0/23APNICValid
37.111.50.0/23APNICValid
37.111.52.0/23APNICValid
37.111.60.0/22APNICValid
37.111.60.0/23APNICValid
37.111.61.0/24APNICValid
37.111.62.0/23APNICValid
37.111.62.0/24APNICValid
37.111.64.0/20APNICValid
37.111.64.0/21APNICValid
37.111.64.0/22APNICValid
37.111.64.0/24APNICValid
37.111.65.0/24APNICValid
37.111.66.0/24APNICValid
37.111.67.0/24APNICValid
37.111.68.0/22APNICValid
37.111.68.0/24APNICValid
37.111.69.0/24APNICValid
37.111.70.0/24APNICValid
37.111.71.0/24APNICValid
37.111.72.0/21APNICValid
37.111.72.0/22APNICValid
37.111.72.0/24APNICValid
37.111.73.0/24APNICValid
37.111.74.0/24APNICValid
37.111.75.0/24APNICValid
37.111.76.0/22APNICValid
37.111.76.0/24APNICValid
37.111.77.0/24APNICValid
37.111.78.0/24APNICValid
37.111.79.0/24APNICValid
37.111.80.0/20APNICValid
37.111.80.0/21APNICValid
37.111.80.0/22APNICValid
37.111.80.0/24APNICValid
37.111.81.0/24APNICValid
37.111.82.0/24APNICValid
37.111.83.0/24APNICValid
37.111.84.0/22APNICValid
37.111.84.0/24APNICValid
37.111.88.0/21APNICValid
37.111.88.0/22APNICValid
37.111.89.0/24APNICValid
37.111.90.0/24APNICValid
37.111.91.0/24APNICValid
37.111.92.0/22APNICValid
37.111.92.0/24APNICValid
37.111.93.0/24APNICValid
37.111.94.0/24APNICValid
37.111.95.0/24APNICValid
37.111.124.0/22APNICValid
37.111.124.0/23APNICValid
37.111.126.0/23APNICValid
103.255.172.64/26APNICValid
103.255.172.128/25APNICValid

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.