bgpreport

Network · data from 2026-11-12

AS61618 Viva Tecnologia Telecomunicações

Registry name: AS61618 - VIVA TECNOLOGIA TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS61618, 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.
45.231.172.0/22 Valid Other IRR onlyTC 671 100% 67
170.81.100.0/22 Valid Other IRR onlyTC 671 100% 67
170.81.102.0/23 Valid Other IRR onlyTC 667 99% 67
2804:376c::/32 Valid Other IRR onlyTC 635 100% 67
2804:376c:8000::/33 Valid Other IRR onlyTC 337 53% 65
2804:376c::/33 Valid Other IRR onlyTC 336 53% 65
45.231.172.0/23 Valid Other IRR onlyTC 137 20% 45
45.231.174.0/23 Valid Other IRR onlyTC 137 20% 45
170.81.100.0/23 Valid Other IRR onlyTC 137 20% 45
2804:376c::/34 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:1000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:2000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:3000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:4000::/34 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:4000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:5000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:6000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:7000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:8000::/34 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:8000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:9000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:a000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:b000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:c000::/34 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:c000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:d000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:e000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
2804:376c:f000::/36 Valid Other IRR onlyTC 2 0%low visibility 2
45.231.172.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
45.231.173.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
45.231.175.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
170.81.100.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
170.81.101.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
170.81.102.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
170.81.103.0/24 Valid Other IRR onlyTC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS61618: TC::AS61618:AS-ANNOUNCEMENTS. 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 (AS61618 isn't in the set, or no route object for AS61618 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 objectsAS61618 in itNot covered
TC::AS61618:AS-ANNOUNCEMENTS TClists itself further down2 member sets in no database: AS267216:AS-ANNOUNCEMENTS, AS267320:AS-ANNOUNCEMENTS 40501,955 Yes 0

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

  • Route object: RIR36
  • AS-SET: missing member2
ChangePrefix or setDetailFull-table peers
Route object: RIR45.231.172.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.81.100.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.81.102.0/23Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:376c::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:376c:8000::/33Route object only in TC. Add it in the RIR database for the space.337 of 636
Route object: RIR2804:376c::/33Route object only in TC. Add it in the RIR database for the space.336 of 636
Route object: RIR45.231.172.0/23Route object only in TC. Add it in the RIR database for the space.137 of 673
Route object: RIR45.231.174.0/23Route object only in TC. Add it in the RIR database for the space.137 of 673
Route object: RIR170.81.100.0/23Route object only in TC. Add it in the RIR database for the space.137 of 673
Route object: RIR2804:376c::/34Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:1000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:2000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:3000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:4000::/34Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:4000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:5000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:6000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:7000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:8000::/34Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:8000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:9000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:a000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:b000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:c000::/34Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:c000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:d000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:e000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR2804:376c:f000::/36Route object only in TC. Add it in the RIR database for the space.2 of 636
Route object: RIR45.231.172.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR45.231.173.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR45.231.175.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR170.81.100.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR170.81.101.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR170.81.102.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR170.81.103.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
AS-SET: missing memberTC::AS61618:AS-ANNOUNCEMENTSAS61618:AS-ANNOUNCEMENTS (TC) lists AS267216:AS-ANNOUNCEMENTS; no IRR database read has it.
AS-SET: missing memberTC::AS61618:AS-ANNOUNCEMENTSAS61618:AS-ANNOUNCEMENTS (TC) lists AS267320:AS-ANNOUNCEMENTS; no IRR database read has it.

Route objects not announced

Every route object with origin AS61618 is announced.

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.