Network report
Who holds an IP address, prefix or AS number, how it is routed (origin AS, RPKI, IRR), its reverse DNS, blocklist listings and PeeringDB record, with what to fix first.
Checking routing, RPKI, reverse DNS, blocklists and the registry. This usually takes 3 to 10 seconds.
Warning: AS45430 (SBN-AWN-IIG-AS-AP) announces 57 IPv4 and 25 IPv6 prefixes. 2 warnings
| AS page | AS45430 |
|---|---|
| Holder | SBN-AWN-IIG-AS-AP - SBN-IIG/AWN-IIG transit provider |
| Allocation | APNIC, Thailand (TH), allocated 2008-09-09 |
| Prefixes (IPv4 / IPv6) | 57 / 25 |
| RPKI valid | 100% (82 / 82) |
| Upstreams and peers | 115 |
| Peering policy | Selective |
What to fix
-
Warning
8 of 82 announced prefixes have no IRR route object: 49.231.115.0/24, 2405:9800:b000::/36, 49.231.122.0/24, 2405:9800:12::/48, 2405:9800:f00f::/48 (+3).
Many networks build their prefix filters from IRR data; without route objects some of them drop the routes.
Fix: Create route (IPv4) and route6 (IPv6) objects with origin AS45430 in your RIR’s IRR database (or RADB).
route: 49.231.115.0/24 origin: AS45430 route6: 2405:9800:b000::/36 origin: AS45430 route: 49.231.122.0/24 origin: AS45430
-
Warning
No public NOC, policy or technical contact.
Other networks use these addresses to set up peering and to reach you during an incident.
Fix: Add a role contact (for example noc@ or peering@ an address you monitor) with visibility Public.
Checks
Routing and RPKI 8 of 82 announced prefixes have no IRR route object: 49.231.115.0/24, 2405:9800:b000::/36, 49.231.122.0/24, 2405:9800:12::/48, 2405:9800:f00f::/48 (+3).
- Pass: AS45430 announces 57 IPv4 and 25 IPv6 prefixes.
- Pass: All 82 announced prefixes are RPKI valid.
- Warning: 8 of 82 announced prefixes have no IRR route object: 49.231.115.0/24, 2405:9800:b000::/36, 49.231.122.0/24, 2405:9800:12::/48, 2405:9800:f00f::/48 (+3).
- Info: 115 upstreams and peers, 43 downstream networks seen.
| Holder | SBN-AWN-IIG-AS-AP - SBN-IIG/AWN-IIG transit provider |
|---|---|
| IPv4 prefixes | 57 |
| IPv6 prefixes | 25 |
| RPKI | 82 valid |
| Without IRR route object | 8 |
| Downstream networks | 43 |
Upstreams and peers seen to the left 115
Announced prefixes 82
Source: RIPEstat (RIPE NCC RIS, Routinator, IRR); AS names: Team Cymru
Open in ASN & BGP prefix lookupRegistration Found at rdap.apnic.net.
- Pass: Found at rdap.apnic.net.
| Name | SBN-AWN-IIG-AS-AP |
|---|---|
| Handle | AS45430 |
| Range | AS45430 |
| Country | TH |
| Status | active |
| Registered | 2008-09-09T01:10:19Z |
| Last changed | 2025-09-22T03:58:32Z |
| Abuse contact | abuseIPv4@sbn.co.th |
| Registry (RIR) | APNIC |
|---|---|
| Country | Thailand (TH) |
| Delegated on | 2008-09-09 |
| Status | Allocated |
| Delegated range | AS45430 |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
| Role | Name | |
|---|---|---|
| abuse | IRT-SUPERBROADBANDNETWORK-TH | abuseIPv4@sbn.co.th |
| registrant | ADVANCED WIRELESS NETWORK COMPANY LIMITED | abuseIPv4@ais.co.th |
| abuse | IRT-AWN-CO-LTD-TH | abuseIPv4@ais.co.th |
| technical, administrative | SBN Co Ltd IP Planning | sitthips@ais.co.th |
Source: https://rdap.apnic.net/autnum/45430. Registration data from rdap.apnic.net, shown under its terms of use (terms): not for marketing or bulk collection.
Open in WHOIS / RDAP lookupPeeringDB No public NOC, policy or technical contact.
- Pass: AS45430 is in PeeringDB as Advanced Wireless Network Co. Ltd.(IIG).
- Info: Peering policy: Selective.
- Info: Present at 15 internet exchanges with 21 ports (1.6T in total).
- Warning: No public NOC, policy or technical contact.
| Network | Advanced Wireless Network Co. Ltd.(IIG) (AWN) |
|---|---|
| AS number | AS45430 |
| Type | Cable/DSL/ISP, Global |
| Website | https://www.awn.co.th/ |
| IRR as-set | AS-SBN-IIG |
| Prefixes (IPv4 / IPv6) | 9000 / 6000 |
| Traffic | 1-5Tbps, Mostly Inbound |
| Peering policy | Selective |
| Locations | Not Required |
| Ratio required | No |
| Contracts | Not Required |
| Last updated | 2026-07-10 |
Source: PeeringDB. Results are cached for an hour.
Open in PeeringDB lookup