bgpreport

Network · data from 2026-11-12

AS271587 Connect House Informática

Registry name: AS271587 - Connect House Informatica Ltda-Me, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271587, 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:7ddc:ffff::/48 No ROA Nonecovered by 2804:7ddc:c000::/34 631 99% 67
179.63.146.0/24 No ROA Other IRR onlyTC 671 100% 67
179.63.144.0/23 No ROA Other IRR onlyRADB, TC 668 99% 67
179.63.147.0/24 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:7ddc::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:7ddc::/33 No ROA Other IRR onlyRADB, TC 347 55% 64
2804:7ddc::/34 No ROA Other IRR onlyTC 347 55% 64
2804:7ddc:4000::/34 No ROA Other IRR onlyTC 347 55% 64
2804:7ddc:8000::/33 No ROA Other IRR onlyRADB, TC 347 55% 64
2804:7ddc:8000::/34 No ROA Other IRR onlyTC 347 55% 64
2804:7ddc:c000::/34 No ROA Other IRR onlyTC 347 55% 64
179.63.144.0/24 No ROA Other IRR onlyTC 202 30% 54
179.63.145.0/24 No ROA Other IRR onlyTC 202 30% 54

AS-SET

PeeringDB's irr_as_set for AS271587: TC::AS271587:AS-CONNECTSPNEW. 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 (AS271587 isn't in the set, or no route object for AS271587 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 objectsAS271587 in itNot covered
TC::AS271587:AS-CONNECTSPNEW TC 2324 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 28 are in fix.csv.

  • ROA: none13
  • Route object: none1
  • Route object: RIR12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:7ddc:ffff::/48No ROA covers it. Add a ROA for AS271587, maxLength 48.631 of 636
Route object: none2804:7ddc:ffff::/48No route object for it. A route object for 2804:7ddc:c000::/34 with origin AS271587 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271587 in the RIR database for the space.631 of 636
ROA: none179.63.146.0/24No ROA covers it. Add a ROA for AS271587, maxLength 24.671 of 673
Route object: RIR179.63.146.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
ROA: none179.63.144.0/23No ROA covers it. Add a ROA for AS271587, maxLength 23.668 of 673
Route object: RIR179.63.144.0/23Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none179.63.147.0/24No ROA covers it. Add a ROA for AS271587, maxLength 24.668 of 673
Route object: RIR179.63.147.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:7ddc::/32No ROA covers it. Add a ROA for AS271587, maxLength 32.635 of 636
Route object: RIR2804:7ddc::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:7ddc::/33No ROA covers it. Add a ROA for AS271587, maxLength 33.347 of 636
Route object: RIR2804:7ddc::/33Route object only in RADB, TC. Add it in the RIR database for the space.347 of 636
ROA: none2804:7ddc::/34No ROA covers it. Add a ROA for AS271587, maxLength 34.347 of 636
Route object: RIR2804:7ddc::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
ROA: none2804:7ddc:4000::/34No ROA covers it. Add a ROA for AS271587, maxLength 34.347 of 636
Route object: RIR2804:7ddc:4000::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
ROA: none2804:7ddc:8000::/33No ROA covers it. Add a ROA for AS271587, maxLength 33.347 of 636
Route object: RIR2804:7ddc:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.347 of 636
ROA: none2804:7ddc:8000::/34No ROA covers it. Add a ROA for AS271587, maxLength 34.347 of 636
Route object: RIR2804:7ddc:8000::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
ROA: none2804:7ddc:c000::/34No ROA covers it. Add a ROA for AS271587, maxLength 34.347 of 636
Route object: RIR2804:7ddc:c000::/34Route object only in TC. Add it in the RIR database for the space.347 of 636
ROA: none179.63.144.0/24No ROA covers it. Add a ROA for AS271587, maxLength 24.202 of 673
Route object: RIR179.63.144.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
ROA: none179.63.145.0/24No ROA covers it. Add a ROA for AS271587, maxLength 24.202 of 673
Route object: RIR179.63.145.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673

Route objects not announced

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

179.63.144.0/22RADB, TCNo ROA
179.63.146.0/23RADB, TCNo 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.