bgpreport

Network · data from 2026-11-12

AS263886 oliveira santos telecomunicacoes ltda

Registry name: AS263886 - oliveira santos telecomunicacoes ltda, BR · PeeringDB

1IPv4 routes 100.0% 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
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS263886, seen from no peer

Announced routes

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

138.204.84.0/22 Valid Other IRR onlyNTTCOM, RADB, TC 667 99% 67
2804:273c::/32 Valid Other IRR onlyRADB, TC 353 56% 65

AS-SET

PeeringDB's irr_as_set for AS263886: AS263886:AS-ESTERNET. 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 (AS263886 isn't in the set, or no route object for AS263886 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 objectsAS263886 in itNot covered
AS263886:AS-ESTERNET TC 118 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.

  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
Route object: RIR138.204.84.0/22Route object only in NTTCOM, RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:273c::/32Route object only in RADB, TC. Add it in the RIR database for the space.353 of 636

Route objects not announced

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

138.204.84.0/23TCValid
138.204.84.0/24TCValid
138.204.85.0/24TCValid
138.204.86.0/23TCValid
138.204.86.0/24TCValid
138.204.87.0/24TCValid

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.