bgpreport

Network · data from 2026-11-12

AS262676 Intervip Telecom

Registry name: AS262676 - Intervip Networks Ltda., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262676, 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.

2804:e80:400::/38 Valid Nonecovered by 2804:e80::/35 105 17% 41
187.73.224.0/21 Valid Other IRR onlyRADB, TC 673 100% 67
187.73.227.0/24 Valid Other IRR onlyRADB, TC 673 100% 67
187.73.229.0/24 Valid Other IRR onlyTC 673 100% 67
187.73.232.0/21 Valid Other IRR onlyRADB, TC 673 100% 67
187.73.224.0/20 Valid Other IRR onlyRADB, TC 672 100% 67
2804:e80::/33 Valid Other IRR onlyRADB, TC 634 100% 68
2804:e80:8000::/33 Valid Other IRR onlyRADB, TC 634 100% 68
2804:e80::/32 Valid Other IRR onlyRADB, TC 633 100% 68
2804:e80::/34 Valid Other IRR onlyTC 104 16% 41
2804:e80:4000::/34 Valid Other IRR onlyTC 104 16% 41
2804:e80:8000::/34 Valid Other IRR onlyTC 104 16% 41
2804:e80:c000::/34 Valid Other IRR onlyTC 104 16% 41
187.73.224.0/23 Valid Other IRR onlyTC 20 3%low visibility 13
187.73.226.0/23 Valid Other IRR onlyTC 20 3%low visibility 13
187.73.228.0/23 Valid Other IRR onlyRADB, TC 20 3%low visibility 13
187.73.230.0/23 Valid Other IRR onlyRADB, TC 20 3%low visibility 13
187.73.232.0/23 Valid Other IRR onlyTC 20 3%low visibility 13
187.73.234.0/23 Valid Other IRR onlyTC 20 3%low visibility 13
187.73.236.0/23 Valid Other IRR onlyTC 20 3%low visibility 13
187.73.238.0/23 Valid Other IRR onlyRADB, TC 20 3%low visibility 13
187.73.224.0/24 Valid Other IRR onlyTC 18 3%low visibility 12
187.73.224.0/22 Valid Other IRR onlyRADB, TC 2 0%low visibility 2
187.73.225.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
187.73.232.0/24 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS262676: AS262676:AS-INTERVIP. 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 (AS262676 isn't in the set, or no route object for AS262676 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 objectsAS262676 in itNot covered
AS262676:AS-INTERVIP TC1 member set in no database: AS-CONECTJA-CUSTOMERS 1618226 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 48 are in fix.csv.

  • Route object: none1
  • Route object: RIR24
  • AS-SET: missing member1
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
Route object: none2804:e80:400::/38No route object for it. A route object for 2804:e80::/35 with origin AS262676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262676 in the RIR database for the space.105 of 636
Route object: RIR187.73.224.0/21Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR187.73.227.0/24Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR187.73.229.0/24Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR187.73.232.0/21Route object only in RADB, TC. Add it in the RIR database for the space.673 of 673
Route object: RIR187.73.224.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:e80::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:e80:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:e80::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:e80::/34Route object only in TC. Add it in the RIR database for the space.104 of 636
Route object: RIR2804:e80:4000::/34Route object only in TC. Add it in the RIR database for the space.104 of 636
Route object: RIR2804:e80:8000::/34Route object only in TC. Add it in the RIR database for the space.104 of 636
Route object: RIR2804:e80:c000::/34Route object only in TC. Add it in the RIR database for the space.104 of 636
Route object: RIR187.73.224.0/23Route object only in TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.226.0/23Route object only in TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.228.0/23Route object only in RADB, TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.230.0/23Route object only in RADB, TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.232.0/23Route object only in TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.234.0/23Route object only in TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.236.0/23Route object only in TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.238.0/23Route object only in RADB, TC. Add it in the RIR database for the space.20 of 673
Route object: RIR187.73.224.0/24Route object only in TC. Add it in the RIR database for the space.18 of 673
Route object: RIR187.73.224.0/22Route object only in RADB, TC. Add it in the RIR database for the space.2 of 673
Route object: RIR187.73.225.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR187.73.232.0/24Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673
AS-SET: missing memberAS262676:AS-INTERVIPAS262676:AS-INTERVIP (TC) lists AS-CONECTJA-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

187.73.226.0/24TCValid
187.73.228.0/22RADB, TCValid
187.73.228.0/24TCValid
187.73.230.0/24TCValid
187.73.231.0/24RADB, TCValid
187.73.232.0/22RADB, TCValid
187.73.233.0/24RADB, TCValid
187.73.234.0/24TCValid
187.73.235.0/24TCValid
187.73.236.0/22RADB, TCValid
187.73.236.0/24TCValid
187.73.237.0/24RADB, TCValid
187.73.238.0/24TCValid
187.73.239.0/24RADBValid
2804:e80::/35TCValid
2804:e80:2000::/35TCValid
2804:e80:4000::/35TCValid
2804:e80:6000::/35TCValid
2804:e80:8000::/35TCValid
2804:e80:a000::/35TCValid
2804:e80:c000::/35TCValid
2804:e80:e000::/35TCValid

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.