bgpreport

Network · data from 2026-11-12

AS13438 Vivio Technologies

Registry name: VIVIO-TECHNOLOGIES - Vivio Technologies, US · PeeringDB

11IPv4 routes 90.9% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS13438, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS13438, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
38.247.84.0/24 No ROA Other IRR onlyRADB 668 99% 67
199.115.216.0/21 Valid Other IRR onlyRADB 673 100% 67
74.114.204.0/22 Valid Other IRR onlyRADB 671 100% 67
162.208.0.0/22 Valid Other IRR onlyRADB 671 100% 67
162.217.168.0/22 Valid Other IRR onlyRADB 671 100% 67
192.231.249.0/24 Valid Other IRR onlyRADB 671 100% 67
204.48.54.0/23 Valid Other IRR onlyRADB 671 100% 67
205.210.188.0/22 Valid Other IRR onlyRADB 671 100% 67
208.77.208.0/22 Valid Other IRR onlyRADB 671 100% 67
199.73.56.0/22 Valid Other IRR onlyRADB 669 99% 67
104.232.42.0/24 Valid RIR databaseARIN, RADB 669 99% 67

AS-SET

AS13438's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 14 are in fix.csv.

  • ROA: none1
  • Route object: RIR10
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none38.247.84.0/24No ROA covers it. Add a ROA for AS13438, maxLength 24.668 of 673
Route object: RIR38.247.84.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR199.115.216.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR74.114.204.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.208.0.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.217.168.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR192.231.249.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR204.48.54.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR205.210.188.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR208.77.208.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR199.73.56.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Route objects with origin AS13438 whose prefix no peer sees AS13438 announce. Many are kept on purpose (backup routes, space announced only in some places).

64.59.192.0/19RADBNo ROA
64.59.192.0/20RADBNo ROA
64.185.192.0/21RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.