bgpreport

Network · data from 2026-11-12

AS266339 Grupo DDSAT

Registry name: AS266339 - JOSE OLIVEIRA DE LIMA DDSAT NET TELECOM E INF - ME, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
1Low visibility seen by under 10% of full-table peers
4Route objects not announced registered with origin AS266339, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266339, 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.
170.239.45.0/24 Valid Other IRR onlyTC 672 100% 67
170.239.44.0/24 Valid Other IRR onlyTC 671 100% 67
170.239.47.0/24 Valid Other IRR onlyTC 670 100% 67
2804:3648:4000::/34 Valid Other IRR onlyTC 630 99% 67
2804:3648:c000::/34 Valid Other IRR onlyTC 630 99% 67
170.239.46.0/24 Valid Other IRR onlyRADB, TC 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS266339: AS266339:RS-ROUTES. 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 (AS266339 isn't in the set, or no route object for AS266339 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 objectsAS266339 in itNot covered
AS266339:RS-ROUTES A route-set, not an AS-SET; route-sets aren't expanded.

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.

  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: RIR170.239.45.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.239.44.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.239.47.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:3648:4000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR2804:3648:c000::/34Route object only in TC. Add it in the RIR database for the space.630 of 636
Route object: RIR170.239.46.0/24Route object only in RADB, TC. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

170.239.44.0/22RADB, TCNo ROA
2804:3648::/32RADB, TCNo ROA
2804:3648::/34TCNo ROA
2804:3648:8000::/34TCNo 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.