bgpreport

Network · data from 2026-11-12

AS267386 P.j. Campos Perina - ME

Registry name: AS267386 - Digital Telecom, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 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
0Route objects not announced registered with origin AS267386, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267386, 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.234.236.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
45.234.236.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
45.234.238.0/24 Valid Other IRR onlyTC 670 100% 66
45.234.237.0/24 Valid Other IRR onlyTC 668 99% 67
2804:4cb4::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:4cb4:1000::/36 Valid Other IRR onlyTC 631 99% 67
2804:4cb4:8000::/36 Valid Other IRR onlyTC 631 99% 67
2804:4cb4:2000::/36 Valid Other IRR onlyTC 630 99% 67

AS-SET

PeeringDB's irr_as_set for AS267386: AS267386: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 (AS267386 isn't in the set, or no route object for AS267386 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 objectsAS267386 in itNot covered
AS267386:AS-ANNOUNCEMENTS TC 128 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: RIR8
ChangePrefix or setDetailFull-table peers
Route object: RIR45.234.236.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.234.236.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.234.238.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.234.237.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:4cb4::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:4cb4:1000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:4cb4:8000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:4cb4:2000::/36Route object only in TC. Add it in the RIR database for the space.630 of 636

Route objects not announced

Every route object with origin AS267386 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.