bgpreport

Network · data from 2026-11-12

AS270949 Vello Serviços de Telecomunicações

Registry name: AS270949 - Vello Servicos de Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270949, 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.224.100.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.224.101.0/24 No ROA Other IRR onlyRADB 670 100% 67
143.137.36.0/22 Valid Other IRR onlyRADB 671 100% 67
2804:73f8::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS270949: AS-52551. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS270949 isn't in the set, or no route object for AS270949 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS270949 in itNot covered
AS-52551 In no IRR database read today.

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 9 are in fix.csv.

  • ROA: none2
  • Route object: RIR4
  • AS-SET: not found1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none38.224.100.0/24No ROA covers it. Add a ROA for AS270949, maxLength 24.672 of 673
Route object: RIR38.224.100.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.224.101.0/24No ROA covers it. Add a ROA for AS270949, maxLength 24.670 of 673
Route object: RIR38.224.101.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR143.137.36.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:73f8::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS-52551PeeringDB names AS-52551; no IRR database read has it.

Route objects not announced

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

38.43.84.0/23ALTDB, RADBNo ROA
38.224.100.0/23RADBNo 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.