Skip to content
KYNEXBGP Toolkit

IRR Lookup

IRR is not RPKI.IRR objects are registrations in routing registries. Anyone with a maintainer account can create them and they are not cryptographically verified, so an IRR route object is not an RPKI authorisation.

Route objects

TypePrefix / keyOriginRegistryMaintainersDescriptionLast modified
route103.174.180.0/23AS147107IDNICMAINT-ID-TUNASMULTIDATARoute Object for 103.174.180.0/23
route103.174.180.0/24AS147107IDNICMAINT-ID-TUNASMULTIDATAPT Tunas Multi Data
route103.174.180.0/24AS147107RADBMAINT-AS7713Proxy-registered route object
route103.174.181.0/24AS147107IDNICMAINT-ID-TUNASMULTIDATAPT Tunas Multi Data
route103.174.181.0/24AS147107RADBMAINT-AS7713Proxy-registered route object
route62400:e420::/32AS147107RADBMAINT-AS55655Customer Route

aut-num

TypePrefix / keyOriginRegistryMaintainersDescriptionLast modified
aut-numAS147107AS147107IDNICMAINT-ID-TUNASMULTIDATAPT Tunas Multi Data

AS-set membership

RegistryAS-sets that include this ASN
RADBAS-PGD, AS-TUNASMULTIDATA-ID, AS-BIZNET, AS147094:AS-MVNET-NAP, AS-NAPCBN, AS-58463, AS64315:AS-MVNET, AS-TIXNET-CUST, AS55655:AS-SIMS, AS-HSP, AS-YAMNET, AS-BERTUAHIX
IDNICAS139967:AS-YAMNET-ID, AS-BERTUAHIX
NTTCOMAS58495:AS-HSP, AS-58463, AS138840:AS-PGD
APNICAS154410:AS-MTL-CUSTOMERS, AS64315:AS-MVNET, AS147094:AS-MVNET-NAP, AS7713:AS-TELKOM-TRANSIT
RIPEAS-YAMNET

Data updated . See limitations.