bgpreport

Network · data from 2026-11-12

AS267560 PC CONNECT TELECOMUNICACOES

Registry name: AS267560 - PC CONNECT TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267560, 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:4348:200::/48 Valid Nonecovered by 2804:4348:200::/40 15 2%low visibility 7
2804:4348:201::/48 Valid Nonecovered by 2804:4348:200::/40 15 2%low visibility 7
181.191.216.0/22 Valid Other IRR onlyALTDB, TC 670 100% 67
2804:4348::/32 Valid Other IRR onlyALTDB, TC 633 100% 67
2804:4348:500::/40 Valid Other IRR onlyALTDB 73 11% 30
181.191.218.0/23 Valid Other IRR onlyALTDB, TC 61 9%low visibility 21
181.191.216.0/23 Valid Other IRR onlyALTDB, TC 60 9%low visibility 21

AS-SET

PeeringDB's irr_as_set for AS267560: AS-CONNECT-ALL. 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 (AS267560 isn't in the set, or no route object for AS267560 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 objectsAS267560 in itNot covered
AS-CONNECT-ALL ALTDBlists itself further down10 member sets in no database: AS-FIBERONE-ALL, AS-FJCEVOLUTION, AS-FNTTELECOM-ALL, AS-JMTELECOM, AS-M-I-MONTREAL-ALL … 2791205,722 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 26 are in fix.csv.

  • Route object: none2
  • Route object: RIR5
  • AS-SET: missing member10
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none2804:4348:200::/48No route object for it. A route object for 2804:4348:200::/40 with origin AS267560 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267560 in the RIR database for the space.15 of 636
Route object: none2804:4348:201::/48No route object for it. A route object for 2804:4348:200::/40 with origin AS267560 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267560 in the RIR database for the space.15 of 636
Route object: RIR181.191.216.0/22Route object only in ALTDB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:4348::/32Route object only in ALTDB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4348:500::/40Route object only in ALTDB. Add it in the RIR database for the space.73 of 636
Route object: RIR181.191.218.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.61 of 673
Route object: RIR181.191.216.0/23Route object only in ALTDB, TC. Add it in the RIR database for the space.60 of 673
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS-FIBERONE-ALL; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS-FJCEVOLUTION; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS-FNTTELECOM-ALL; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS-JMTELECOM; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS-M-I-MONTREAL-ALL; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS-TRIBENET-ALL; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS264301:AS-LNP-TELECOM; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS264301:AS-LNP-TELECOM-ALL; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS265393:AS-ANNOUNCEMENTS; no IRR database read has it.
AS-SET: missing memberAS-CONNECT-ALLAS-CONNECT-ALL (ALTDB) lists AS270728:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

181.191.216.0/24ALTDB, TCValid
181.191.217.0/24ALTDB, TCValid
181.191.218.0/24TCValid
181.191.219.0/24TCValid
2804:4348::/40ALTDBInvalid: maxLength
2804:4348:100::/40ALTDBInvalid: maxLength
2804:4348:200::/40ALTDBInvalid: maxLength
2804:4348:300::/40ALTDBInvalid: maxLength
2804:4348:400::/40ALTDBInvalid: maxLength

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.