Describe the bug
The PeeringDB web interface fails to recognize a valid, recently assigned ASN from APNIC/IDNIC. It returns an error: "This ASN is not assigned by any RIR," preventing account affiliation even though the ASN is clearly visible in official WHOIS records.

To Reproduce
Steps to reproduce the behavior:

Log in to a PeeringDB account.

Go to the Profile page.

Under the Affiliate with organization section, enter ASN: 153910.

Enter Organization Name: PT Ryza Data Nusantara.

Click Affiliate.

See error message: "This ASN is not assigned by any RIR."

Expected behavior
The system should validate the ASN against the RIR database (APNIC) and allow the affiliation process to proceed for a valid, assigned ASN.

Who is affected by the problem?
New network operators or existing organizations assigned with fresh 4-byte ASN blocks (specifically in the 15xxxx range from APNIC/IDNIC).

What is the impact?
Network operators cannot create or update their PeeringDB profiles, which delays the establishment of peering sessions and interconnection with other networks/IXPs.

Are there security concerns?
No.

Are there privacy concerns?
No.

What are the proposed actions?
Investigate the synchronization/caching mechanism between PeeringDB's local database and the APNIC/IDNIC RIR source to ensure "fresh" assignments are picked up more rapidly or to allow manual bypass when WHOIS is confirmed.

What is the proposed priority?
Urgent (as it blocks new members from using the platform).

Provide a rationale for any/all of the above
PeeringDB support confirmed via ticket that the ASN is visible in WHOIS (APNIC modification time: 2026-03-09), yet the automated system continues to reject it. This indicates a significant lag or failure in the automated RIR data ingestion process.

Additional context
Support ticket mentioned that the modification at APNIC might have been later than the initial registration attempt, but the error persists even after the WHOIS record is fully propagated and confirmed by staff.