bgpreport

Network · data from 2026-11-12

AS272814 TOVARSAT C.A.

Registry name: AS272814 - TOVARSAT C.A., VE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272814, 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.255.222.0/23 Invalid: origin None 71 11% 36
74.118.61.0/24 Valid Nonecovered by 74.118.60.0/22 669 99% 67
74.118.62.0/24 Valid Nonecovered by 74.118.60.0/22 669 99% 67
2803:4490:1::/48 Valid Nonecovered by 2803:4490::/32 631 99% 67
2803:4490::/48 Valid Nonecovered by 2803:4490::/32 630 99% 67
74.118.63.0/24 Valid Other IRR onlyRADB 670 100% 68
74.118.60.0/24 Valid Other IRR onlyRADB 669 99% 67
2803:4490::/32 Valid Other IRR onlyRADB 631 99% 67

AS-SET

AS272814'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 10 are in fix.csv.

  • ROA: origin1
  • Route object: none5
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin38.255.222.0/23ROAs covering it name AS53338, not AS272814. If AS272814 should announce it, add a ROA for AS272814.71 of 673
Route object: none38.255.222.0/23No route object for it. Add a route object with origin AS272814 in the RIR database for the space.71 of 673
Route object: none74.118.61.0/24No route object for it. A route object for 74.118.60.0/22 with origin AS272814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272814 in the RIR database for the space.669 of 673
Route object: none74.118.62.0/24No route object for it. A route object for 74.118.60.0/22 with origin AS272814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272814 in the RIR database for the space.669 of 673
Route object: none2803:4490:1::/48No route object for it. A route object for 2803:4490::/32 with origin AS272814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272814 in the RIR database for the space.631 of 636
Route object: none2803:4490::/48No route object for it. A route object for 2803:4490::/32 with origin AS272814 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272814 in the RIR database for the space.630 of 636
Route object: RIR74.118.63.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR74.118.60.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2803:4490::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

74.118.60.0/22ARIN, RADBValid

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.