bgpreport

Network · data from 2026-11-12

AS45785 TECHAVENUE Malaysia

Registry name: TECHAVENUE-AP - TechAvenue Malaysia, MY · PeeringDB

16IPv4 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
2Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS45785, seen from no peer

Announced routes

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

183.78.168.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
183.78.169.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
183.78.170.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
183.78.171.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
202.43.100.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
202.43.101.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
202.43.102.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 68
210.1.224.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
210.1.225.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
210.1.226.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
210.1.227.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
210.1.228.0/24 Valid RIR databaseAPNIC, NTTCOM, REACH 670 100% 68
210.1.229.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
210.1.230.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
210.1.231.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 68
202.43.103.0/24 Valid RIR databaseAPNIC, NTTCOM 47 7%low visibility 33
2401:c400:3000::/48 Valid RIR databaseAPNIC 47 7%low visibility 34

AS-SET

AS45785'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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

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

27.122.58.0/24APNICValid
27.122.59.0/24APNICValid
43.245.198.0/24APNICValid
103.10.196.0/24APNICValid
116.193.157.0/24RADBValid
202.43.100.0/23RADBNo ROA
210.1.224.0/21APNICValid
210.1.224.0/22APNICValid
210.1.228.0/22APNIC, NTTCOMValid
2401:c400::/32APNIC, RADBValid
2401:c400:1000::/48APNIC, RADBValid
2401:c400:2000::/48APNIC, RADBValid
2401:c400:4000::/48APNICValid
2401:c400:5000::/48APNICValid
2401:c400:6000::/48APNICValid
2401:c400:7000::/48APNICValid
2401:c400:8000::/48APNICValid
2401:c400:9000::/48APNICValid

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.