140.126.0.0/16
Nobody announces 140.126.0.0/16 on its own; it is covered by 140.112.0.0/12 AS1659 ERX-TANET-ASN1. Seen by 0 of our 5 looking glass sessions.
Summary
What the table says about 140.126.0.0/16
Prefix
Origin
not announced
Size
65,536 addresses
Less specific
More specifics
0
IRR route objects
2 exact, 4 covering
RPKI
Route origin authorizations
| ROA prefix | Max length | Authorized origin | Trust anchor |
|---|---|---|---|
| 140.126.0.0/16 | /16 | AS9916 NCTU-TW | APNIC |
| 140.112.0.0/12 | /12 | AS1659 ERX-TANET-ASN1 | APNIC |
IRR
Route objects
Registered in the IRR for this prefix and the ones covering it. Look it up live.
| Route | Origin | Source | Description | Maintained by |
|---|---|---|---|---|
| 140.126.0.0/16 | AS9916 NCTU-TW | NTTCOM | NCTU (proxy-registered route object) | MAINT-ASNET |
| 140.126.0.0/16 | AS9505 TWGATE-AP | REACH | REACH (Customer Route) | MAINT-REACH-NOC |
| 140.112.0.0/12 covering | AS17717 MOECC-IPV6 | LEVEL3 | Proxy-registered route object. Workaround the IRR filter issue for TANet. Because they forgot to add value on their PeeringDB as-set field. | XINGXUNTECHLTD-MNT |
| 140.112.0.0/12 covering | AS1659 ERX-TANET-ASN1 | NTTCOM | TANET (proxy-registered route object) | MAINT-ASNET |
| 140.112.0.0/12 covering | AS1659 ERX-TANET-ASN1 | RADB | Transit Customer AS1659 (TANet) of EBIX (AS17709) | MAINT-AS17709 |
| 140.112.0.0/12 covering | AS9505 TWGATE-AP | REACH | REACH (Customer Route) | MAINT-REACH-NOC |
Less specific
Covering prefixes
Announced prefixes that contain this one, most specific first.