bgpreport

Network · data from 2026-11-12

AS271154 AS271154 - IHG SERVICOS TELECOM

Registry name: AS271154 - IHG SERVICOS TELECOM, BR · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 83.3% with a route object
4IPv6 routes 0.0% RPKI valid · 75.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
9No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
30Route objects not announced registered with origin AS271154, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271154, 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.
131.255.82.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2804:7718:c000::/48 No ROA Nonecovered by 2804:7718:c000::/36 627 99% 67
179.42.147.0/24 No ROA Other IRR onlyRADB 672 100% 67
179.42.144.0/23 No ROA Other IRR onlyRADB 666 99% 66
179.42.145.0/24 No ROA Other IRR onlyRADB 666 99% 66
179.42.144.0/24 No ROA Other IRR onlyRADB 665 99% 66
179.42.146.0/24 No ROA Other IRR onlyRADB 663 99% 67
2804:7718:c000::/34 No ROA Other IRR onlyRADB 635 100% 67
2804:7718::/34 No ROA Other IRR onlyRADB 631 99% 67
2804:7718:4000::/34 No ROA Other IRR onlyRADB 631 99% 67

AS-SET

AS271154 isn't in PeeringDB, where networks name their AS-SET.

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 50 are in fix.csv.

  • ROA: origin1
  • ROA: none9
  • Route object: none2
  • Route object: RIR8
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: origin131.255.82.0/24ROAs covering it name AS264470, not AS271154. If AS271154 should announce it, add a ROA for AS271154.1 of 673
Route object: none131.255.82.0/24Route objects for it name AS264470. Add a route object with origin AS271154 in the RIR database for the space.1 of 673
ROA: none2804:7718:c000::/48No ROA covers it. Add a ROA for AS271154, maxLength 48.627 of 636
Route object: none2804:7718:c000::/48No route object for it. A route object for 2804:7718:c000::/36 with origin AS271154 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271154 in the RIR database for the space.627 of 636
ROA: none179.42.147.0/24No ROA covers it. Add a ROA for AS271154, maxLength 24.672 of 673
Route object: RIR179.42.147.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none179.42.144.0/23No ROA covers it. Add a ROA for AS271154, maxLength 23.666 of 673
Route object: RIR179.42.144.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none179.42.145.0/24No ROA covers it. Add a ROA for AS271154, maxLength 24.666 of 673
Route object: RIR179.42.145.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none179.42.144.0/24No ROA covers it. Add a ROA for AS271154, maxLength 24.665 of 673
Route object: RIR179.42.144.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none179.42.146.0/24No ROA covers it. Add a ROA for AS271154, maxLength 24.663 of 673
Route object: RIR179.42.146.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673
ROA: none2804:7718:c000::/34No ROA covers it. Add a ROA for AS271154, maxLength 34.635 of 636
Route object: RIR2804:7718:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:7718::/34No ROA covers it. Add a ROA for AS271154, maxLength 34.631 of 636
Route object: RIR2804:7718::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:7718:4000::/34No ROA covers it. Add a ROA for AS271154, maxLength 34.631 of 636
Route object: RIR2804:7718:4000::/34Route object only in RADB. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

179.42.144.0/22RADBNo ROA
179.42.146.0/23RADBNo ROA
2804:7718::/32RADBNo ROA
2804:7718::/33RADBNo ROA
2804:7718::/35RADBNo ROA
2804:7718::/36RADBNo ROA
2804:7718:1000::/36RADBNo ROA
2804:7718:2000::/35RADBNo ROA
2804:7718:2000::/36RADBNo ROA
2804:7718:3000::/36RADBNo ROA
2804:7718:4000::/35RADBNo ROA
2804:7718:4000::/36RADBNo ROA
2804:7718:5000::/36RADBNo ROA
2804:7718:6000::/35RADBNo ROA
2804:7718:6000::/36RADBNo ROA
2804:7718:7000::/36RADBNo ROA
2804:7718:8000::/33RADBNo ROA
2804:7718:8000::/34RADBNo ROA
2804:7718:8000::/35RADBNo ROA
2804:7718:8000::/36RADBNo ROA
2804:7718:9000::/36RADBNo ROA
2804:7718:a000::/35RADBNo ROA
2804:7718:a000::/36RADBNo ROA
2804:7718:b000::/36RADBNo ROA
2804:7718:c000::/35RADBNo ROA
2804:7718:c000::/36RADBNo ROA
2804:7718:d000::/36RADBNo ROA
2804:7718:e000::/35RADBNo ROA
2804:7718:e000::/36RADBNo ROA
2804:7718:f000::/36RADBNo 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.