Loading
AS MEMBERSHIP
AS45557 is a member of the following AS sets:
- AS-24086 Internet Exchange Provider
- AS-7602 Saigon Postel Global IP Network transit customers
- AS-HANOITELECOM ASes to which we provide transit (+ our AS)
- AS-FPT FPT Telecom Company
- AS-TWIG Chunghwa Telecom Co., Ltd. International Bus
- AS-VNPT VNPT Net's transit customers
- AS-7552 Internet eXchange Provider - Viettel Corporation
- AS-HUTCHCITY Hutchcity
- AS-HGC-INTL HGC INTL
- AS3491:AS-CUSTOMERS-NA PCCW Global Customers in North America
- AS-IIJ ASes routed by IIJ
- AS-REACH-CUSTOMERS AS List of REACH customers
- AS-45903 CMCTELECOM-VN
- AS7643:AS-CUSTOMERS IP Transit Customers of VNPT
- AS-HURRICANEV6 HE.NET AS MACRO
- AS3491:AS-CUSTOMERS-AP PCCW Global Customers in Asia/Pacific
- AS45896:AS-PPS Mobifone Global IP Transit Customer
- AS-TELSTRA-INTL-CUSTOMERS AS List of TI(AS4637) customers
- AS-45899CUST Transit customer
- AS-FPT_COMMUNICATIONS FPT Telecom Company
- AS-45899 VNPT Net
AUTONOMOUS SYSTEM
AS45557 VNTT-AS-VN source:APNIC
| aut-num | AS45557 |
| as-name | VNTT-AS-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| descr | No 21 VSIP II, Road 1, Vietnam Singapore II,Hoa Phu ward,Thu Dau Mot City,Binh Duong |
| country | VN |
| import | from AS7643 action pref=100; accept AS45557 |
| import | from AS7552 action pref=100; accept AS45557 |
| import | from AS38248 action pref=100; accept AS45557 |
| export | to AS7643 announce AS45557 |
| export | to AS7552 announce AS45557 |
| export | to AS38248 announce AS45557 |
| admin-c | DNHV1-AP |
| tech-c | NNB6-AP |
| mnt-by | MAINT-VN-VNNIC |
| mnt-irt | IRT-VNNIC-AP |
| mnt-routes | MAINT-VN-VNNIC |
| last-modified | 2017-11-19T08:53:10Z |
| source | APNIC |
AS45557 VNTT-AS-VN source:RADB
| aut-num | AS45557 |
| as-name | VNTT-AS-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| descr | T4 No1 way, Vietnam Singapore IPZ, Ben Cat, Binh Duong |
| admin-c | ATD-70 |
| tech-c | LPC-72 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20101109 |
| source | RADB |
| last-modified | 2023-11-13T15:41:14Z |
REGISTERED ROUTES
45.118.136.0/22 route object of VNTT source:NTTCOM
| route | 45.118.136.0/22 |
| descr | route object of VNTT |
| origin | AS45557 |
| remarks | this route is from VIETTEL |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20150730 |
| source | NTTCOM |
| rpki-ov-state | valid |
45.118.136.0/22 VNTT-VN source:APNIC
| route | 45.118.136.0/22 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:41:44Z |
| source | APNIC |
| rpki-ov-state | valid |
45.118.136.0/22 45.118.136.0/22 source:RADB
| route | 45.118.136.0/22 |
| descr | 45.118.136.0/22 |
| origin | AS45557 |
| mnt-by | MAINT-AS7602 |
| changed | lanh.ho@spt.vn 20160219 |
| source | RADB |
| last-modified | 2023-11-13T15:48:45Z |
| rpki-ov-state | valid |
45.118.136.0/24 route object of VNTT source:NTTCOM
| route | 45.118.136.0/24 |
| descr | route object of VNTT |
| origin | AS45557 |
| remarks | this route is from VIETTEL |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20150707 |
| source | NTTCOM |
| rpki-ov-state | valid |
45.118.136.0/24 VNTTT 45.118.136.0/24 source:RADB
| route | 45.118.136.0/24 |
| descr | VNTTT 45.118.136.0/24 |
| origin | AS45557 |
| mnt-by | MAINT-AS7602 |
| changed | lanh.ho@spt.vn 20160129 |
| source | RADB |
| last-modified | 2023-11-13T15:48:32Z |
| rpki-ov-state | valid |
45.118.136.0/24 VNTT-VN source:APNIC
| route | 45.118.136.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:41:47Z |
| source | APNIC |
| rpki-ov-state | valid |
45.118.137.0/24 Proxy-registered route object source:RADB
| route | 45.118.137.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | matthew.chan@hgc.com.hk |
| mnt-by | MAINT-HGC-INTL |
| changed | matthew.chan@hgc.com.hk 20171104 |
| source | RADB |
| last-modified | 2023-11-13T15:52:21Z |
| rpki-ov-state | valid |
45.118.137.0/24 VNTT-VN source:APNIC
| route | 45.118.137.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:41:49Z |
| source | APNIC |
| rpki-ov-state | valid |
45.118.137.0/24 route object of VNTT source:NTTCOM
| route | 45.118.137.0/24 |
| descr | route object of VNTT |
| origin | AS45557 |
| remarks | this route is from VIETTEL |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20150730 |
| source | NTTCOM |
| rpki-ov-state | valid |
45.118.138.0/24 route object of VNTT source:NTTCOM
| route | 45.118.138.0/24 |
| descr | route object of VNTT |
| origin | AS45557 |
| remarks | this route is from VIETTEL |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20150730 |
| source | NTTCOM |
| rpki-ov-state | valid |
45.118.138.0/24 VNTT-VN source:APNIC
| route | 45.118.138.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:41:52Z |
| source | APNIC |
| rpki-ov-state | valid |
45.118.138.0/24 Proxy-registered route object source:RADB
| route | 45.118.138.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | matthew.chan@hgc.com.hk |
| mnt-by | MAINT-HGC-INTL |
| changed | matthew.chan@hgc.com.hk 20171104 |
| source | RADB |
| last-modified | 2023-11-13T15:52:21Z |
| rpki-ov-state | valid |
45.118.139.0/24 route object of VNTT source:NTTCOM
| route | 45.118.139.0/24 |
| descr | route object of VNTT |
| origin | AS45557 |
| remarks | this route is from VIETTEL |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20150730 |
| source | NTTCOM |
| rpki-ov-state | valid |
45.118.139.0/24 45.118.139.0/24 VNTT source:RADB
| route | 45.118.139.0/24 |
| descr | 45.118.139.0/24 VNTT |
| origin | AS45557 |
| mnt-by | MAINT-AS7602 |
| changed | lanh.ho@spt.vn 20160321 |
| source | RADB |
| last-modified | 2023-11-13T15:48:54Z |
| rpki-ov-state | valid |
45.118.139.0/24 VNTT-VN source:APNIC
| route | 45.118.139.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:41:55Z |
| source | APNIC |
| rpki-ov-state | valid |
103.17.88.0/22 VNTT-VN source:APNIC
| route | 103.17.88.0/22 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:43:02Z |
| source | APNIC |
| rpki-ov-state | valid |
103.17.88.0/22 103.17.88.0/22 source:RADB
| route | 103.17.88.0/22 |
| descr | 103.17.88.0/22 |
| origin | AS45557 |
| mnt-by | MAINT-AS7602 |
| changed | lanh.ho@spt.vn 20160219 |
| source | RADB |
| last-modified | 2023-11-13T15:48:45Z |
| rpki-ov-state | valid |
103.17.88.0/22 CUSTOMER OF VIETTEL source:NTTCOM
| route | 103.17.88.0/22 |
| descr | CUSTOMER OF VIETTEL |
| origin | AS45557 |
| remarks | this is non-portable space, no exceptions |
| notify | minhna4@viettel.com.vn |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20131113 |
| source | NTTCOM |
| rpki-ov-state | valid |
103.17.88.0/24 CMI IP Transit source:NTTCOM
| route | 103.17.88.0/24 |
| descr | CMI IP Transit |
| origin | AS45557 |
| admin-c | MAINT-CMI-INT-HK |
| tech-c | MAINT-CMI-INT-HK |
| mnt-by | MAINT-CMI-INT-HK |
| changed | qas_support@cmi.chinamobile.com 20180620 |
| source | NTTCOM |
| rpki-ov-state | valid |
103.17.88.0/24 VNTT AS45557 source:RADB
| route | 103.17.88.0/24 |
| descr | VNTT AS45557 |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20150821 |
| source | RADB |
| last-modified | 2023-11-13T15:48:06Z |
| rpki-ov-state | valid |
103.17.88.0/24 VNTT-VN source:APNIC
| route | 103.17.88.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:43:04Z |
| source | APNIC |
| rpki-ov-state | valid |
103.17.89.0/24 VNTT JSC source:NTTCOM
| route | 103.17.89.0/24 |
| descr | VNTT JSC |
| origin | AS45557 |
| remarks | this route is from AS45557 VNTT JSC |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20151202 |
| source | NTTCOM |
| rpki-ov-state | valid |
103.17.89.0/24 CMI (Customer Route) source:RADB
| route | 103.17.89.0/24 |
| descr | CMI (Customer Route) |
| origin | AS45557 |
| mnt-by | MAINT-AS58453 |
| changed | qas_support@cmi.chinamobile.com 20180620 |
| source | RADB |
| last-modified | 2023-11-13T15:54:00Z |
| rpki-ov-state | valid |
103.17.89.0/24 VNTT-VN source:APNIC
| route | 103.17.89.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:43:07Z |
| source | APNIC |
| rpki-ov-state | valid |
103.17.90.0/24 VNTT JSC source:NTTCOM
| route | 103.17.90.0/24 |
| descr | VNTT JSC |
| origin | AS45557 |
| remarks | this route is from AS45557 VNTT JSC |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20151202 |
| source | NTTCOM |
| rpki-ov-state | valid |
103.17.90.0/24 VNTT-VN source:APNIC
| route | 103.17.90.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:43:10Z |
| source | APNIC |
| rpki-ov-state | valid |
103.17.90.0/24 CMI (Customer Route) source:RADB
| route | 103.17.90.0/24 |
| descr | CMI (Customer Route) |
| origin | AS45557 |
| mnt-by | MAINT-AS58453 |
| changed | qas_support@cmi.chinamobile.com 20180620 |
| source | RADB |
| last-modified | 2023-11-13T15:54:00Z |
| rpki-ov-state | valid |
103.17.91.0/24 VNTT-VN source:APNIC
| route | 103.17.91.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:43:12Z |
| source | APNIC |
| rpki-ov-state | valid |
103.17.91.0/24 CMI (Customer Route) source:RADB
| route | 103.17.91.0/24 |
| descr | CMI (Customer Route) |
| origin | AS45557 |
| mnt-by | MAINT-AS58453 |
| changed | qas_support@cmi.chinamobile.com 20180620 |
| source | RADB |
| last-modified | 2023-11-13T15:54:00Z |
| rpki-ov-state | valid |
103.17.91.0/24 VNTT JSC source:NTTCOM
| route | 103.17.91.0/24 |
| descr | VNTT JSC |
| origin | AS45557 |
| remarks | this route is from AS45557 VNTT JSC |
| mnt-by | MAINT-VIETTEL |
| changed | minhna4@viettel.com.vn 20151202 |
| source | NTTCOM |
| rpki-ov-state | valid |
103.129.80.0/22 TTDVVT-VNTT-VN source:APNIC
| route | 103.129.80.0/22 |
| descr | TTDVVT-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:44:21Z |
| source | APNIC |
| rpki-ov-state | valid |
103.129.80.0/22 TTDVVT-VNTT-VN,Vietnam Technology and Telecommunication JSC source:RADB
| route | 103.129.80.0/22 |
| descr | TTDVVT-VNTT-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20180907 |
| source | RADB |
| last-modified | 2023-11-13T15:54:40Z |
| rpki-ov-state | valid |
103.129.80.0/24 TTDVVT-VNTT-VN source:APNIC
| route | 103.129.80.0/24 |
| descr | TTDVVT-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:44:24Z |
| source | APNIC |
| rpki-ov-state | valid |
103.129.80.0/24 TTDVVT-VNTT-VN,Vietnam Technology and Telecommunication JSC source:RADB
| route | 103.129.80.0/24 |
| descr | TTDVVT-VNTT-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20180907 |
| source | RADB |
| last-modified | 2023-11-13T15:54:40Z |
| rpki-ov-state | valid |
103.129.81.0/24 TTDVVT-VNTT-VN,Vietnam Technology and Telecommunication JSC source:RADB
| route | 103.129.81.0/24 |
| descr | TTDVVT-VNTT-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20180907 |
| source | RADB |
| last-modified | 2023-11-13T15:54:40Z |
| rpki-ov-state | valid |
103.129.81.0/24 TTDVVT-VNTT-VN source:APNIC
| route | 103.129.81.0/24 |
| descr | TTDVVT-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:44:26Z |
| source | APNIC |
| rpki-ov-state | valid |
103.129.82.0/24 TTDVVT-VNTT-VN source:APNIC
| route | 103.129.82.0/24 |
| descr | TTDVVT-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:44:29Z |
| source | APNIC |
| rpki-ov-state | valid |
103.129.82.0/24 TTDVVT-VNTT-VN,Vietnam Technology and Telecommunication JSC source:RADB
| route | 103.129.82.0/24 |
| descr | TTDVVT-VNTT-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20180907 |
| source | RADB |
| last-modified | 2023-11-13T15:54:40Z |
| rpki-ov-state | valid |
103.129.83.0/24 TTDVVT-VNTT-VN source:APNIC
| route | 103.129.83.0/24 |
| descr | TTDVVT-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-06T02:44:32Z |
| source | APNIC |
| rpki-ov-state | valid |
103.129.83.0/24 TTDVVT-VNTT-VN,Vietnam Technology and Telecommunication JSC source:RADB
| route | 103.129.83.0/24 |
| descr | TTDVVT-VNTT-VN |
| descr | Vietnam Technology and Telecommunication JSC |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20180907 |
| source | RADB |
| last-modified | 2023-11-13T15:54:40Z |
| rpki-ov-state | valid |
103.153.218.0/23 Vietnam Internet Network Information Center (VNNIC),18 Nguyen Du Str, Hai Ba Trung District, Hanoi City, Vietnam,24th floor, VNTA Tower, Duong Dinh Nghe, Cau Giay, Hanoi source:APNIC
| route | 103.153.218.0/23 |
| origin | AS45557 |
| descr | Vietnam Internet Network Information Center (VNNIC) |
| descr | 18 Nguyen Du Str, Hai Ba Trung District, Hanoi City, Vietnam |
| descr | 24th floor, VNTA Tower, Duong Dinh Nghe, Cau Giay, Hanoi |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:19:24Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.218.0/24 HP-VNTT-VN source:APNIC
| route | 103.153.218.0/24 |
| descr | HP-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:03:38Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.219.0/24 HP-VNTT-VN source:APNIC
| route | 103.153.219.0/24 |
| descr | HP-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:03:41Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.220.0/23 Vietnam Internet Network Information Center (VNNIC),18 Nguyen Du Str, Hai Ba Trung District, Hanoi City, Vietnam,24th floor, VNTA Tower, Duong Dinh Nghe, Cau Giay, Hanoi source:APNIC
| route | 103.153.220.0/23 |
| origin | AS45557 |
| descr | Vietnam Internet Network Information Center (VNNIC) |
| descr | 18 Nguyen Du Str, Hai Ba Trung District, Hanoi City, Vietnam |
| descr | 24th floor, VNTA Tower, Duong Dinh Nghe, Cau Giay, Hanoi |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:05:38Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.220.0/24 NA-VNTT-VN source:APNIC
| route | 103.153.220.0/24 |
| descr | NA-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:04:31Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.221.0/24 NA-VNTT-VN source:APNIC
| route | 103.153.221.0/24 |
| descr | NA-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:04:34Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.222.0/23 Vietnam Internet Network Information Center (VNNIC),18 Nguyen Du Str, Hai Ba Trung District, Hanoi City, Vietnam,24th floor, VNTA Tower, Duong Dinh Nghe, Cau Giay, Hanoi source:APNIC
| route | 103.153.222.0/23 |
| origin | AS45557 |
| descr | Vietnam Internet Network Information Center (VNNIC) |
| descr | 18 Nguyen Du Str, Hai Ba Trung District, Hanoi City, Vietnam |
| descr | 24th floor, VNTA Tower, Duong Dinh Nghe, Cau Giay, Hanoi |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:19:03Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.222.0/24 QN-VNTT-VN source:APNIC
| route | 103.153.222.0/24 |
| descr | QN-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:05:12Z |
| source | APNIC |
| rpki-ov-state | valid |
103.153.223.0/24 QN-VNTT-VN source:APNIC
| route | 103.153.223.0/24 |
| descr | QN-VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2020-11-12T00:05:15Z |
| source | APNIC |
| rpki-ov-state | valid |
103.170.248.0/23 VNTT-SOLUTIONS-VN source:APNIC
| route | 103.170.248.0/23 |
| descr | VNTT-SOLUTIONS-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:19:46Z |
| source | APNIC |
| rpki-ov-state | valid |
103.170.248.0/24 VNTT-SOLUTIONS-VN source:APNIC
| route | 103.170.248.0/24 |
| descr | VNTT-SOLUTIONS-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:19:48Z |
| source | APNIC |
| rpki-ov-state | valid |
103.170.249.0/24 VNTT-SOLUTIONS-VN source:APNIC
| route | 103.170.249.0/24 |
| descr | VNTT-SOLUTIONS-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:19:51Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.0.0/21 VNTT-VN source:APNIC
| route | 180.148.0.0/21 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:11Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.0.0/21 Proxy-registered route object source:NTTCOM
| route | 180.148.0.0/21 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| remarks | This is a HGC customer route-object |
| remarks | which is being exported under this origin AS. |
| remarks | : |
| remarks | This route object was created because no existing |
| remarks | route object with the same origin was found. |
| remarks | : |
| remarks | Please contact radb@hutchcity.com if you have any |
| remarks | questions regarding this object. |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20171104 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.0.0/21 Proxy-registered route object source:RADB
| route | 180.148.0.0/21 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.0.0/22 Proxy-registered route object source:NTTCOM
| route | 180.148.0.0/22 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| remarks | This is a HGC customer route-object |
| remarks | which is being exported under this origin AS. |
| remarks | : |
| remarks | This route object was created because no existing |
| remarks | route object with the same origin was found. |
| remarks | : |
| remarks | Please contact radb@hutchcity.com if you have any |
| remarks | questions regarding this object. |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20171104 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.0.0/22 Proxy-registered route object source:RADB
| route | 180.148.0.0/22 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.0.0/22 VNTT-VN source:APNIC
| route | 180.148.0.0/22 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:13Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.0.0/23 VNTT-VN source:APNIC
| route | 180.148.0.0/23 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:16Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.0.0/23 Proxy-registered route object source:RADB
| route | 180.148.0.0/23 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.0.0/23 Proxy-registered route object source:NTTCOM
| route | 180.148.0.0/23 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| remarks | This is a HGC customer route-object |
| remarks | which is being exported under this origin AS. |
| remarks | : |
| remarks | This route object was created because no existing |
| remarks | route object with the same origin was found. |
| remarks | : |
| remarks | Please contact radb@hutchcity.com if you have any |
| remarks | questions regarding this object. |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20171104 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.0.0/24 Proxy-registered route object source:NTTCOM
| route | 180.148.0.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| remarks | This is a HGC customer route-object |
| remarks | which is being exported under this origin AS. |
| remarks | : |
| remarks | This route object was created because no existing |
| remarks | route object with the same origin was found. |
| remarks | : |
| remarks | Please contact radb@hutchcity.com if you have any |
| remarks | questions regarding this object. |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20171104 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.0.0/24 VNTT-VN source:APNIC
| route | 180.148.0.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:19Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.0.0/24 Proxy-registered route object source:RADB
| route | 180.148.0.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.1.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.1.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.1.0/24 Proxy-registered route object source:RADB
| route | 180.148.1.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.1.0/24 VNTT-VN source:APNIC
| route | 180.148.1.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:22Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.2.0/23 VNTT-VN source:APNIC
| route | 180.148.2.0/23 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:25Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.2.0/23 route object of AS45557 source:NTTCOM
| route | 180.148.2.0/23 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.2.0/23 Proxy-registered route object source:RADB
| route | 180.148.2.0/23 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.2.0/24 VNTT-VN source:APNIC
| route | 180.148.2.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:28Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.2.0/24 Proxy-registered route object source:RADB
| route | 180.148.2.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.2.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.2.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.3.0/24 Proxy-registered route object source:RADB
| route | 180.148.3.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.3.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.3.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.3.0/24 VNTT-VN source:APNIC
| route | 180.148.3.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:32Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.4.0/22 VNTT-VN source:APNIC
| route | 180.148.4.0/22 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:35Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.4.0/22 route object of AS45557 source:NTTCOM
| route | 180.148.4.0/22 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.4.0/22 Proxy-registered route object source:RADB
| route | 180.148.4.0/22 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.4.0/23 VNTT-VN source:APNIC
| route | 180.148.4.0/23 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:38Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.4.0/23 route object of AS45557 source:NTTCOM
| route | 180.148.4.0/23 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.4.0/23 Proxy-registered route object source:RADB
| route | 180.148.4.0/23 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.4.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.4.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.4.0/24 VNTT-VN source:APNIC
| route | 180.148.4.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:41Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.4.0/24 Proxy-registered route object source:RADB
| route | 180.148.4.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.5.0/24 Proxy-registered route object source:RADB
| route | 180.148.5.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.5.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.5.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.5.0/24 VNTT-VN source:APNIC
| route | 180.148.5.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:44Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.6.0/23 VNTT-VN source:APNIC
| route | 180.148.6.0/23 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:47Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.6.0/23 route object of AS45557 source:NTTCOM
| route | 180.148.6.0/23 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.6.0/23 Proxy-registered route object source:RADB
| route | 180.148.6.0/23 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.6.0/24 Proxy-registered route object source:RADB
| route | 180.148.6.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.6.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.6.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
180.148.6.0/24 VNTT-VN source:APNIC
| route | 180.148.6.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:50Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.7.0/24 VNTT-VN source:APNIC
| route | 180.148.7.0/24 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:18:52Z |
| source | APNIC |
| rpki-ov-state | valid |
180.148.7.0/24 Proxy-registered route object source:RADB
| route | 180.148.7.0/24 |
| descr | Proxy-registered route object |
| origin | AS45557 |
| notify | radb@hutchcity.com |
| mnt-by | MAINT-AS9304 |
| changed | radb@hutchcity.com 20121101 |
| source | RADB |
| last-modified | 2023-11-13T15:44:28Z |
| rpki-ov-state | valid |
180.148.7.0/24 route object of AS45557 source:NTTCOM
| route | 180.148.7.0/24 |
| descr | route object of AS45557 |
| origin | AS45557 |
| remarks | this route is original from VNTT |
| mnt-by | MAINT-VIETTEL |
| changed | nthai@viettel.com.vn 20120827 |
| source | NTTCOM |
| rpki-ov-state | valid |
2404:3a00::/44 VNTT-VN source:APNIC
| route6 | 2404:3a00::/44 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:02Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00::/44 VNTT source:RADB
| route6 | 2404:3a00::/44 |
| origin | AS45557 |
| descr | VNTT |
| mnt-by | MAINT-AS45899 |
| changed | radb@vnpt.vn 20220524 |
| source | RADB |
| last-modified | 2023-11-13T16:11:22Z |
| rpki-ov-state | valid |
2404:3a00::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:05Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:08Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:11Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:14Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00::/48 Vietnam Technology and Telecommunication JSC source:RADB
| route6 | 2404:3a00::/48 |
| descr | Vietnam Technology and Telecommunication JSC |
| origin | AS45557 |
| mnt-by | MAINT-AS18403 |
| changed | netadmin@fpt.vn 20160219 |
| source | RADB |
| last-modified | 2023-11-13T15:48:45Z |
| rpki-ov-state | valid |
2404:3a00:1::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:17Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:2::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:20Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:23Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:33Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:4::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:36Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:4::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:39Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:42Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:45Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:6::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:6::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:48Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:6::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:6::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:51Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:7::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:7::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:54Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:8::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:8::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:21:58Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:8::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:8::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:8::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:8::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:04Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:8::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:8::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:13Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:9::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:9::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:16Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:a::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:a::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:19Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:a::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:a::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:22Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:b::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:b::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:25Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:c::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:c::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:28Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:c::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:c::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:31Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:c::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:c::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:34Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:d::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:d::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:42Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:e::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:e::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:45Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:e::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:e::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:48Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:f::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:f::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:22:52Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:10::/44 VNTT-VN source:APNIC
| route6 | 2404:3a00:10::/44 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:10Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:10::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:10::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:13Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:10::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:10::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:18Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:10::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:10::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:21Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:10::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:10::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:24Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:11::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:11::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:27Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:12::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:12::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:30Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:12::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:12::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:33Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:13::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:13::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:36Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:14::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:14::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:39Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:14::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:14::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:42Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:14::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:14::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:45Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:15::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:15::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:48Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:16::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:16::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:51Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:16::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:16::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:54Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:17::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:17::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:30:57Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:18::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:18::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:18::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:18::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:04Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:18::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:18::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:07Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:18::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:18::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:10Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:19::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:19::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:13Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1a::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:1a::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:16Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1a::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1a::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:19Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1b::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1b::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:22Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1c::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:1c::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:25Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1c::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:1c::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:27Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1c::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1c::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:30Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1d::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1d::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:33Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1e::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:1e::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:36Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1e::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1e::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:39Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:1f::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:1f::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:31:44Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:20::/44 VNTT-VN source:APNIC
| route6 | 2404:3a00:20::/44 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:24Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:20::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:20::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:27Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:20::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:20::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:30Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:20::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:20::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:33Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:20::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:20::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:36Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:21::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:21::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:39Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:22::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:22::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:42Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:22::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:22::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:45Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:23::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:23::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:49Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:24::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:24::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:52Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:24::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:24::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:55Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:24::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:24::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:58Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:25::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:25::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:26::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:26::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:04Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:26::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:26::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:07Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:27::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:27::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:10Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:28::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:28::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:13Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:28::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:28::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:16Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:28::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:28::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:19Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:28::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:28::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:21Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:29::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:29::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:24Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2a::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:2a::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:27Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2a::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2a::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:30Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2b::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2b::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:33Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2c::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:2c::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:36Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2c::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:2c::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:39Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2c::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2c::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:42Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2d::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2d::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:46Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2e::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:2e::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:49Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2e::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2e::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:52Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:2f::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:2f::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:29:55Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:30::/44 VNTT-VN source:APNIC
| route6 | 2404:3a00:30::/44 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:08Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:30::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:30::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:11Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:30::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:30::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:14Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:30::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:30::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:17Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:30::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:30::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:20Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:31::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:31::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:23Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:32::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:32::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:26Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:32::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:32::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:29Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:33::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:33::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:32Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:34::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:34::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:40Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:34::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:34::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:43Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:34::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:34::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:46Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:35::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:35::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:50Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:36::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:36::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:53Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:36::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:36::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:56Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:37::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:37::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:23:59Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:38::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:38::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:02Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:38::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:38::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:05Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:38::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:38::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:08Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:38::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:38::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:11Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:39::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:39::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:14Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3a::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:3a::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:17Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3a::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3a::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:20Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3b::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3b::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:23Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3c::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:3c::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:26Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3c::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:3c::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:29Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3c::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3c::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:32Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3d::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3d::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:35Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3e::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:3e::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:38Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3e::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3e::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:40Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:3f::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:3f::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:43Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:40::/44 VNTT-VN source:APNIC
| route6 | 2404:3a00:40::/44 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:40Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:40::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:40::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:43Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:40::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:40::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:46Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:40::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:40::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:50Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:40::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:40::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:52Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:41::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:41::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:55Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:42::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:42::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:58Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:42::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:42::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:43::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:43::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:04Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:44::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:44::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:08Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:44::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:44::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:11Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:44::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:44::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:14Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:45::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:45::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:17Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:46::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:46::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:20Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:46::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:46::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:23Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:47::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:47::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:26Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:48::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:48::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:29Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:48::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:48::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:33Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:48::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:48::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:36Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:48::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:48::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:39Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:49::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:49::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:42Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4a::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:4a::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:45Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4a::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4a::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:48Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4b::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4b::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:51Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4c::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:4c::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:54Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4c::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:4c::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:27:58Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4c::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4c::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4d::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4d::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:04Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4e::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:4e::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:07Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4e::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4e::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:10Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:4f::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:4f::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:28:13Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:50::/44 VNTT-VN source:APNIC
| route6 | 2404:3a00:50::/44 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:55Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:50::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:50::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:24:58Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:50::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:50::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:50::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:50::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:04Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:50::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:50::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:07Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:51::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:51::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:10Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:52::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:52::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:13Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:52::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:52::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:16Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:53::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:53::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:19Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:54::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:54::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:22Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:54::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:54::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:25Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:54::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:54::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:28Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:55::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:55::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:31Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:56::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:56::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:34Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:56::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:56::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:37Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:57::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:57::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:40Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:58::/45 VNTT-VN source:APNIC
| route6 | 2404:3a00:58::/45 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:43Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:58::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:58::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:46Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:58::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:58::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:49Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:58::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:58::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:52Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:59::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:59::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:55Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5a::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:5a::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:25:58Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5a::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5a::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:01Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5b::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5b::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:06Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5c::/46 VNTT-VN source:APNIC
| route6 | 2404:3a00:5c::/46 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:09Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5c::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:5c::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:12Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5c::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5c::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:15Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5d::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5d::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:18Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5e::/47 VNTT-VN source:APNIC
| route6 | 2404:3a00:5e::/47 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:21Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5e::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5e::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:24Z |
| source | APNIC |
| rpki-ov-state | valid |
2404:3a00:5f::/48 VNTT-VN source:APNIC
| route6 | 2404:3a00:5f::/48 |
| descr | VNTT-VN |
| origin | AS45557 |
| mnt-by | MAINT-VN-VNNIC |
| last-modified | 2022-02-09T05:26:29Z |
| source | APNIC |
| rpki-ov-state | valid |
