bgpreport

Network · data from 2026-11-12

AS262908 D. A. Comercio e Servicos de Informatica

Registry name: AS262908 - D. A. Comercio e Servicos de Informatica Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262908, 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:3c8::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 68
2804:3c8::/33 No ROA Other IRR onlyALTDB 2 0%low visibility 2
2804:3c8:8000::/33 No ROA Other IRR onlyALTDB 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS262908: AS-JATOCONECT. 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 (AS262908 isn't in the set, or no route object for AS262908 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 objectsAS262908 in itNot covered
AS-JATOCONECT ALTDB 125 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 8 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:3c8::/32No ROA covers it. Add a ROA for AS262908, maxLength 32.635 of 636
Route object: RIR2804:3c8::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:3c8::/33No ROA covers it. Add a ROA for AS262908, maxLength 33.2 of 636
Route object: RIR2804:3c8::/33Route object only in ALTDB. Add it in the RIR database for the space.2 of 636
ROA: none2804:3c8:8000::/33No ROA covers it. Add a ROA for AS262908, maxLength 33.2 of 636
Route object: RIR2804:3c8:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

177.52.56.0/22ALTDB, RADBNo ROA
177.91.136.0/22ALTDB, RADBNo 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.